Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1e8bf11d04af157e943ca8d27189096a6611bf2c56aac6caa11b413fbf2a12a2

Tx prefix hash: 4a1f76b6c35cbc41f88960abd5fbb5803d3f79daa29b992b46f1882468552ac6
Tx public key: 9adadd90759ef96969b73bd8a82964cf8368208b3c5e13fe1e12f6bc415c99cf
Timestamp: 1726136417 Timestamp [UCT]: 2024-09-12 10:20:17 Age [y:d:h:m:s]: 01:055:17:20:32
Block: 1108425 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298236 RingCT/type: yes/0
Extra: 019adadd90759ef96969b73bd8a82964cf8368208b3c5e13fe1e12f6bc415c99cf021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b27a1771b967b525c13e2f4f707038f8403cb266ea0ac47208fe3cc9fcafab98 0.600000000000 1586316 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": 1108435, "vin": [ { "gen": { "height": 1108425 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b27a1771b967b525c13e2f4f707038f8403cb266ea0ac47208fe3cc9fcafab98" } } ], "extra": [ 1, 154, 218, 221, 144, 117, 158, 249, 105, 105, 183, 59, 216, 168, 41, 100, 207, 131, 104, 32, 139, 60, 94, 19, 254, 30, 18, 246, 188, 65, 92, 153, 207, 2, 17, 0, 0, 0, 4, 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