Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14890ddf43b05f5c341041dc79e2419e184e402180fa8eb44b6a1a2b150246d6

Tx prefix hash: 65fdd4d1025dc641118e1a90acc23a7b110cae3a17d2c22d7c301b9fbd07bb6d
Tx public key: 483ec127191c04d1df0c83bca14957def3ee1c0f9462320abab981432a14a50d
Timestamp: 1718443559 Timestamp [UCT]: 2024-06-15 09:25:59 Age [y:d:h:m:s]: 00:277:08:40:07
Block: 1044664 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198201 RingCT/type: yes/0
Extra: 01483ec127191c04d1df0c83bca14957def3ee1c0f9462320abab981432a14a50d021100000001cd63fb1b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d88828429cb15d491c22c9846e911049b27ae4d20d761ff8492c2d090383191d 0.600000000000 1514031 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": 1044674, "vin": [ { "gen": { "height": 1044664 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d88828429cb15d491c22c9846e911049b27ae4d20d761ff8492c2d090383191d" } } ], "extra": [ 1, 72, 62, 193, 39, 25, 28, 4, 209, 223, 12, 131, 188, 161, 73, 87, 222, 243, 238, 28, 15, 148, 98, 50, 10, 186, 185, 129, 67, 42, 20, 165, 13, 2, 17, 0, 0, 0, 1, 205, 99, 251, 27, 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