Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31feef5884480a8a0f524ff1a39c88f206a561ff515b5d70261d68b6a3fbabb7

Tx prefix hash: 0d034930b0febd10d8b7170184be2b3356f768a1d085b9b457f0699f15126869
Tx public key: c353d661f5bfdfb7d5964fc8c91660becc886a0acd6e143b5b0e9c880a9916d6
Timestamp: 1713850393 Timestamp [UCT]: 2024-04-23 05:33:13 Age [y:d:h:m:s]: 01:191:02:32:46
Block: 1006577 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395222 RingCT/type: yes/0
Extra: 01c353d661f5bfdfb7d5964fc8c91660becc886a0acd6e143b5b0e9c880a9916d60211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14f64cf308a8d27a884ed2caaed3e1e73c62b18aefd5b10769357aba3d85fb15 0.600000000000 1467647 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": 1006587, "vin": [ { "gen": { "height": 1006577 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14f64cf308a8d27a884ed2caaed3e1e73c62b18aefd5b10769357aba3d85fb15" } } ], "extra": [ 1, 195, 83, 214, 97, 245, 191, 223, 183, 213, 150, 79, 200, 201, 22, 96, 190, 204, 136, 106, 10, 205, 110, 20, 59, 91, 14, 156, 136, 10, 153, 22, 214, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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