Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14bbd2a99cc16f0b895fd001541b5d76fb7277fcbc473e5760bd61c53bbc2947

Tx prefix hash: 4ad1c8f22208f2a347768f6c59a86bcc7fefb8d2bebce49fe9c9474584b5c995
Tx public key: a7a23b2df94b4fdb75e2daf9fc47ff4fe8dfa354581bfa42c32954847545dcd3
Timestamp: 1737194094 Timestamp [UCT]: 2025-01-18 09:54:54 Age [y:d:h:m:s]: 00:337:10:55:53
Block: 1199951 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238725 RingCT/type: yes/0
Extra: 01a7a23b2df94b4fdb75e2daf9fc47ff4fe8dfa354581bfa42c32954847545dcd30211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45858c3b57da3f1ad4d3e5e9ab7db5b4546614367681bbca646d09f7583074ed 0.600000000000 1686592 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": 1199961, "vin": [ { "gen": { "height": 1199951 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45858c3b57da3f1ad4d3e5e9ab7db5b4546614367681bbca646d09f7583074ed" } } ], "extra": [ 1, 167, 162, 59, 45, 249, 75, 79, 219, 117, 226, 218, 249, 252, 71, 255, 79, 232, 223, 163, 84, 88, 27, 250, 66, 195, 41, 84, 132, 117, 69, 220, 211, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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