Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de984a497d521edc07e46170a951284d5e77d7702991155598655e216930b3cd

Tx prefix hash: 074165003fd55ce143000be86bcdef517f2ea9816a3351a3c665ec16fb95c439
Tx public key: cf4a7c8a7c154ac721bc3bb7a9ffdb5d2e61fb26c44e6abde749a0ecf360040d
Timestamp: 1724768735 Timestamp [UCT]: 2024-08-27 14:25:35 Age [y:d:h:m:s]: 00:294:08:38:17
Block: 1097088 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210158 RingCT/type: yes/0
Extra: 01cf4a7c8a7c154ac721bc3bb7a9ffdb5d2e61fb26c44e6abde749a0ecf360040d021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b510af9465f5c6d5545d581a66a8d972e94b6a01e468bb9029420cfba2e31b9 0.600000000000 1572383 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": 1097098, "vin": [ { "gen": { "height": 1097088 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b510af9465f5c6d5545d581a66a8d972e94b6a01e468bb9029420cfba2e31b9" } } ], "extra": [ 1, 207, 74, 124, 138, 124, 21, 74, 199, 33, 188, 59, 183, 169, 255, 219, 93, 46, 97, 251, 38, 196, 78, 106, 189, 231, 73, 160, 236, 243, 96, 4, 13, 2, 17, 0, 0, 0, 7, 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