Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5ecc429ec3777b014f160c61f1f7cbe7d6122f2a533806857f9248ce8d962d8

Tx prefix hash: db272c0d9ba54fd393da55bf00af7ad9a75e087db7fb563863a0d5f1c53fff51
Tx public key: cf47d203a51b38e02b66aa00812b11b9882dd6dbdf96ffb73508f5b88100d5c8
Timestamp: 1736911209 Timestamp [UCT]: 2025-01-15 03:20:09 Age [y:d:h:m:s]: 00:155:17:23:56
Block: 1197608 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110986 RingCT/type: yes/0
Extra: 01cf47d203a51b38e02b66aa00812b11b9882dd6dbdf96ffb73508f5b88100d5c8021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 11cf315bc597611654920d9f9c2cdb687a16899338f741e5d9c383aa630bff54 0.600000000000 1684221 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": 1197618, "vin": [ { "gen": { "height": 1197608 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11cf315bc597611654920d9f9c2cdb687a16899338f741e5d9c383aa630bff54" } } ], "extra": [ 1, 207, 71, 210, 3, 165, 27, 56, 224, 43, 102, 170, 0, 129, 43, 17, 185, 136, 45, 214, 219, 223, 150, 255, 183, 53, 8, 245, 184, 129, 0, 213, 200, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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