Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c355f5e2c0b914345a0bbcb626d20c120110541a010dc3d8e30519b623b4851

Tx prefix hash: b1aa700c948a787787ee3750db372638e4b61c0bdf86353a7f11b43f93dbf095
Tx public key: 37d0cd4d718c4f88e272dcba41cdecb55dacd4f2548903bb37cac59b112a95a8
Timestamp: 1726488095 Timestamp [UCT]: 2024-09-16 12:01:35 Age [y:d:h:m:s]: 00:116:01:17:31
Block: 1111344 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82987 RingCT/type: yes/0
Extra: 0137d0cd4d718c4f88e272dcba41cdecb55dacd4f2548903bb37cac59b112a95a8021100000011e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ef49880b5330ca6e0a708e0c1d82e5ec34725009be5ac97d64173b281ee26b4 0.600000000000 1590271 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": 1111354, "vin": [ { "gen": { "height": 1111344 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ef49880b5330ca6e0a708e0c1d82e5ec34725009be5ac97d64173b281ee26b4" } } ], "extra": [ 1, 55, 208, 205, 77, 113, 140, 79, 136, 226, 114, 220, 186, 65, 205, 236, 181, 93, 172, 212, 242, 84, 137, 3, 187, 55, 202, 197, 155, 17, 42, 149, 168, 2, 17, 0, 0, 0, 17, 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