Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cb6e4f39225687d74d0f6b78e5594defc590a85f53490dbbf59be0e9e98e228

Tx prefix hash: d2bab5830d615f788a810fafbf04437d23a4e90f863e807c6bdb4b6778e4bed0
Tx public key: 8d379a1bcad7d57d0b707511dd8535483d3fd6b69c16b7b6d0ab2f68ca9c37ae
Timestamp: 1638307053 Timestamp [UCT]: 2021-11-30 21:17:33 Age [y:d:h:m:s]: 03:335:22:08:48
Block: 385632 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1016506 RingCT/type: yes/0
Extra: 018d379a1bcad7d57d0b707511dd8535483d3fd6b69c16b7b6d0ab2f68ca9c37ae021100000006d6e4826b000000000000000000

1 output(s) for total of 32.377362897000 dcy

stealth address amount amount idx
00: 1c6b2fdc1641bb351bb578d822822bc8a39c1c3629e88252841e1e97c8901e27 32.377362897000 778179 of 0

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": 385642, "vin": [ { "gen": { "height": 385632 } } ], "vout": [ { "amount": 32377362897, "target": { "key": "1c6b2fdc1641bb351bb578d822822bc8a39c1c3629e88252841e1e97c8901e27" } } ], "extra": [ 1, 141, 55, 154, 27, 202, 215, 213, 125, 11, 112, 117, 17, 221, 133, 53, 72, 61, 63, 214, 182, 156, 22, 183, 182, 208, 171, 47, 104, 202, 156, 55, 174, 2, 17, 0, 0, 0, 6, 214, 228, 130, 107, 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