Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3d7172cf00d0cc024db137e2d80feba7dd16c05a047fa92dba92c07d37b3f84

Tx prefix hash: 65898f3c968f56651c82e4a0b1097538d0b4a80289df545793f5f1df2dda828f
Tx public key: 3022c1c10b73e8d42f4a52ca276085850dfa1e8f077e38bb038c5bfae6ca4056
Timestamp: 1728757807 Timestamp [UCT]: 2024-10-12 18:30:07 Age [y:d:h:m:s]: 00:171:01:01:58
Block: 1130167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 122015 RingCT/type: yes/0
Extra: 013022c1c10b73e8d42f4a52ca276085850dfa1e8f077e38bb038c5bfae6ca405602110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf1cf572f22d697fa4a162e35507127a6d55963690039b4571e86f6a6c72cdaf 0.600000000000 1613040 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": 1130177, "vin": [ { "gen": { "height": 1130167 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf1cf572f22d697fa4a162e35507127a6d55963690039b4571e86f6a6c72cdaf" } } ], "extra": [ 1, 48, 34, 193, 193, 11, 115, 232, 212, 47, 74, 82, 202, 39, 96, 133, 133, 13, 250, 30, 143, 7, 126, 56, 187, 3, 140, 91, 250, 230, 202, 64, 86, 2, 17, 0, 0, 0, 5, 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