Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 84c1b60fa1ecf14d8ac870c015e0540ba5c7cdf5643aa15bfd45815d5bb803ed

Tx prefix hash: d72b9b4fd6c9ddccde5fd04a2f57307a754c564026d3fbd769739007b4356ebf
Tx public key: 490ea7d33c861af282acd37a550135583e53c67efb6ad1c672bc9edd48cefb67
Timestamp: 1722703671 Timestamp [UCT]: 2024-08-03 16:47:51 Age [y:d:h:m:s]: 00:270:22:40:52
Block: 1079966 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193565 RingCT/type: yes/0
Extra: 01490ea7d33c861af282acd37a550135583e53c67efb6ad1c672bc9edd48cefb6702110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d947ad8d5eb559838430e1201546e3c8b24b12c2d02cfbd69d3f83679829cfe 0.600000000000 1553143 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1079976, "vin": [ { "gen": { "height": 1079966 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d947ad8d5eb559838430e1201546e3c8b24b12c2d02cfbd69d3f83679829cfe" } } ], "extra": [ 1, 73, 14, 167, 211, 60, 134, 26, 242, 130, 172, 211, 122, 85, 1, 53, 88, 62, 83, 198, 126, 251, 106, 209, 198, 114, 188, 158, 221, 72, 206, 251, 103, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8