Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed2c21828cd670c6c990b92cef9568684dc0b37da49da48b67a4406ba43c96fc

Tx prefix hash: cc3007503ac552b53f01af006afed17e39dad87a103c5e489fdc2f9888087db9
Tx public key: 0777fb6bfc9f5b8b39590e4586ad42bea0f3caf99acf1c3e20b94f62ccd592e6
Timestamp: 1686548945 Timestamp [UCT]: 2023-06-12 05:49:05 Age [y:d:h:m:s]: 01:158:05:16:13
Block: 780490 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 374439 RingCT/type: yes/0
Extra: 010777fb6bfc9f5b8b39590e4586ad42bea0f3caf99acf1c3e20b94f62ccd592e602110000000233af99f4000000000000000000

1 output(s) for total of 1.591889036000 dcy

stealth address amount amount idx
00: ba9e1ca235ea7c715db127b52116b8ba1b02aa68a9fff315fcfe1174d60e09a1 1.591889036000 1230197 of 0

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": 780500, "vin": [ { "gen": { "height": 780490 } } ], "vout": [ { "amount": 1591889036, "target": { "key": "ba9e1ca235ea7c715db127b52116b8ba1b02aa68a9fff315fcfe1174d60e09a1" } } ], "extra": [ 1, 7, 119, 251, 107, 252, 159, 91, 139, 57, 89, 14, 69, 134, 173, 66, 190, 160, 243, 202, 249, 154, 207, 28, 62, 32, 185, 79, 98, 204, 213, 146, 230, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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