Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b06d7c4631a26c29333f13ff6e0c55ca0d52ae5fba8872954acd79eee28d7a15

Tx prefix hash: 9a5a1ddc6dcbbe20591f6ccd48236515738289494c11fbfc15c6795e724a3f95
Tx public key: 7b3604f28f64452abaa2af45b53ca5ecfb99f977458931691d78efe2a13a75f8
Timestamp: 1728222120 Timestamp [UCT]: 2024-10-06 13:42:00 Age [y:d:h:m:s]: 00:170:01:16:16
Block: 1125721 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121319 RingCT/type: yes/0
Extra: 017b3604f28f64452abaa2af45b53ca5ecfb99f977458931691d78efe2a13a75f802110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f3c1a7d1a16a946419b40e45d9ccde27f850f0a300dbab10d93c1db3585fd98 0.600000000000 1608472 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": 1125731, "vin": [ { "gen": { "height": 1125721 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f3c1a7d1a16a946419b40e45d9ccde27f850f0a300dbab10d93c1db3585fd98" } } ], "extra": [ 1, 123, 54, 4, 242, 143, 100, 69, 42, 186, 162, 175, 69, 181, 60, 165, 236, 251, 153, 249, 119, 69, 137, 49, 105, 29, 120, 239, 226, 161, 58, 117, 248, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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