Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed0dfc58e857b58c889969dfc49e30b6a71eecc9d9acf4dc49a86b70abfcaa38

Tx prefix hash: 8f7e673d414913d3d7ab211ef5b29af635d08e3c8c78a44f2548dac88d9beccd
Tx public key: 912cfe80fbd7a10bb1fe15403f83619ea542313843048aaeef84362827e95cd9
Timestamp: 1734993036 Timestamp [UCT]: 2024-12-23 22:30:36 Age [y:d:h:m:s]: 00:104:10:07:26
Block: 1181750 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74397 RingCT/type: yes/0
Extra: 01912cfe80fbd7a10bb1fe15403f83619ea542313843048aaeef84362827e95cd90211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34ac2a6f23ac1dcfb4cfd07679c60bbac0aac1a902fb6f14045c2b67d7f0c6f8 0.600000000000 1668175 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": 1181760, "vin": [ { "gen": { "height": 1181750 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34ac2a6f23ac1dcfb4cfd07679c60bbac0aac1a902fb6f14045c2b67d7f0c6f8" } } ], "extra": [ 1, 145, 44, 254, 128, 251, 215, 161, 11, 177, 254, 21, 64, 63, 131, 97, 158, 165, 66, 49, 56, 67, 4, 138, 174, 239, 132, 54, 40, 39, 233, 92, 217, 2, 17, 0, 0, 0, 9, 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