Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 49bdb1dc497a5067d3b5531584e1fff8b7b1307e374479126915d45cab114c9d

Tx prefix hash: e9885dc01806b44ddebc699870d9441ff98315e53f1142b3e939215b45dff4d1
Tx public key: f2ef77c0544e09a4dbe14ea4b55062a8547c73141da117f7e909edbf0380d99e
Timestamp: 1721879594 Timestamp [UCT]: 2024-07-25 03:53:14 Age [y:d:h:m:s]: 00:256:15:19:36
Block: 1073130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183330 RingCT/type: yes/0
Extra: 01f2ef77c0544e09a4dbe14ea4b55062a8547c73141da117f7e909edbf0380d99e021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0d451c08f98ec840ae167aa8b362822e5803dc22c3f6bdb6c3f2e0057b809fe 0.600000000000 1545629 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": 1073140, "vin": [ { "gen": { "height": 1073130 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0d451c08f98ec840ae167aa8b362822e5803dc22c3f6bdb6c3f2e0057b809fe" } } ], "extra": [ 1, 242, 239, 119, 192, 84, 78, 9, 164, 219, 225, 78, 164, 181, 80, 98, 168, 84, 124, 115, 20, 29, 161, 23, 247, 233, 9, 237, 191, 3, 128, 217, 158, 2, 17, 0, 0, 0, 6, 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