Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83a58bc1c68588ac7e3e5cb8da461be36f39e79909afe47a8ef6f449da99289e

Tx prefix hash: 4a4a9aa27f6c0f5935a825d6055996c6187e2237a43c02de8cd403403c6ecfba
Tx public key: f6ff0632e95e35ba87151d1a63e1b0e1baad50bcf61e0a62cf043fb13a4e3b37
Timestamp: 1722000641 Timestamp [UCT]: 2024-07-26 13:30:41 Age [y:d:h:m:s]: 00:276:22:49:28
Block: 1074142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197869 RingCT/type: yes/0
Extra: 01f6ff0632e95e35ba87151d1a63e1b0e1baad50bcf61e0a62cf043fb13a4e3b3702110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0bfaca08e80b32b502b962e28bc6a1084e8cfdd58880b59067604ddceddc7ab2 0.600000000000 1546655 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": 1074152, "vin": [ { "gen": { "height": 1074142 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0bfaca08e80b32b502b962e28bc6a1084e8cfdd58880b59067604ddceddc7ab2" } } ], "extra": [ 1, 246, 255, 6, 50, 233, 94, 53, 186, 135, 21, 29, 26, 99, 225, 176, 225, 186, 173, 80, 188, 246, 30, 10, 98, 207, 4, 63, 177, 58, 78, 59, 55, 2, 17, 0, 0, 0, 10, 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