Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2cf01e189f1bf296855f931e34a893bf367f6846d97e7702eba12a5b058aa538

Tx prefix hash: 863dc6ee2a28cfdeb50983d79dc23dcf4aa03b86f88f58700e34c5cf048ce5f2
Tx public key: e466403915b110a1db16f8566f60e4e043a76df0c034ce8e992123c6f1f327bf
Timestamp: 1728715354 Timestamp [UCT]: 2024-10-12 06:42:34 Age [y:d:h:m:s]: 00:167:07:06:49
Block: 1129804 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119353 RingCT/type: yes/0
Extra: 01e466403915b110a1db16f8566f60e4e043a76df0c034ce8e992123c6f1f327bf02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a694495797b04839b62f813324faf16380fc94dec959aa7209fb1c3abe48cc17 0.600000000000 1612667 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": 1129814, "vin": [ { "gen": { "height": 1129804 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a694495797b04839b62f813324faf16380fc94dec959aa7209fb1c3abe48cc17" } } ], "extra": [ 1, 228, 102, 64, 57, 21, 177, 16, 161, 219, 22, 248, 86, 111, 96, 228, 224, 67, 167, 109, 240, 192, 52, 206, 142, 153, 33, 35, 198, 241, 243, 39, 191, 2, 17, 0, 0, 0, 2, 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