Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83c2fda4b0ba02d53ebef82538a6cb998ca019d62d3a0b256f606f53516bf712

Tx prefix hash: 232c464410c11dbd619b49258a939753df04b05ee862d7b0f6d311dc86b1f543
Tx public key: bf54d5f8e72be03225855b128a829c7d4151395a95ebc6a8f150f75c6d613be7
Timestamp: 1730846590 Timestamp [UCT]: 2024-11-05 22:43:10 Age [y:d:h:m:s]: 00:154:21:38:53
Block: 1147384 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110540 RingCT/type: yes/0
Extra: 01bf54d5f8e72be03225855b128a829c7d4151395a95ebc6a8f150f75c6d613be702110000000b007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 53dd5b5de5ef168a125d613e82b061cbc5aff380859132e373416c34d281354d 0.600000000000 1632079 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": 1147394, "vin": [ { "gen": { "height": 1147384 } } ], "vout": [ { "amount": 600000000, "target": { "key": "53dd5b5de5ef168a125d613e82b061cbc5aff380859132e373416c34d281354d" } } ], "extra": [ 1, 191, 84, 213, 248, 231, 43, 224, 50, 37, 133, 91, 18, 138, 130, 156, 125, 65, 81, 57, 90, 149, 235, 198, 168, 241, 80, 247, 92, 109, 97, 59, 231, 2, 17, 0, 0, 0, 11, 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