Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ddab1d1527da86e6db859e64acff4d1a6e316cd86482f9b7dfa43216c5d3002d

Tx prefix hash: a41021a0e303ac89f011c2ea78e468e2104b77ca33aa206ba8365acf13ad121e
Tx public key: 78879ebe2bd40ea62716a23ec5c5dffa7aae77be0a6b2adba2aca6a70fddf8a5
Timestamp: 1722963866 Timestamp [UCT]: 2024-08-06 17:04:26 Age [y:d:h:m:s]: 00:168:22:34:22
Block: 1082121 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120824 RingCT/type: yes/0
Extra: 0178879ebe2bd40ea62716a23ec5c5dffa7aae77be0a6b2adba2aca6a70fddf8a502110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ce2d343d9242ee5555ced3c522c1a020adfed4e22e5236ffdeca80435b1e2c8e 0.600000000000 1555944 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": 1082131, "vin": [ { "gen": { "height": 1082121 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ce2d343d9242ee5555ced3c522c1a020adfed4e22e5236ffdeca80435b1e2c8e" } } ], "extra": [ 1, 120, 135, 158, 190, 43, 212, 14, 166, 39, 22, 162, 62, 197, 197, 223, 250, 122, 174, 119, 190, 10, 107, 42, 219, 162, 172, 166, 167, 15, 221, 248, 165, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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