Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6414c2341630a7465c85d80925b47508a03931233245d380773735e86252ea7e

Tx prefix hash: 7147d4bbb3fa727c13251ecbb9d9a2fbfa40fc62fa8c56c0a5471da18d2d4817
Tx public key: 3dcc272f74ae4f92c8a5dac69d9396049f2d83e993397225627760feefa8b1c0
Timestamp: 1723582902 Timestamp [UCT]: 2024-08-13 21:01:42 Age [y:d:h:m:s]: 00:161:14:30:11
Block: 1087260 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115560 RingCT/type: yes/0
Extra: 013dcc272f74ae4f92c8a5dac69d9396049f2d83e993397225627760feefa8b1c0021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b4fcf4286110f38fb289006e2a4dca2416b736169d13083eb5b44b6bfccedca 0.600000000000 1561867 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": 1087270, "vin": [ { "gen": { "height": 1087260 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b4fcf4286110f38fb289006e2a4dca2416b736169d13083eb5b44b6bfccedca" } } ], "extra": [ 1, 61, 204, 39, 47, 116, 174, 79, 146, 200, 165, 218, 198, 157, 147, 150, 4, 159, 45, 131, 233, 147, 57, 114, 37, 98, 119, 96, 254, 239, 168, 177, 192, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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