Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e313cf820225933c9769383dd8fe4cd23c2f037226b807b5b392d352d6005b24

Tx prefix hash: 881276090df91e5ce63cf629216795a6794a0fdb9ffb9052222cb102b2dfff00
Tx public key: 29dd851e82d8ae66e4835f6bbbf807f0d4e627fb06b642f11e2851090c5986c1
Timestamp: 1729262063 Timestamp [UCT]: 2024-10-18 14:34:23 Age [y:d:h:m:s]: 00:020:14:02:42
Block: 1134346 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 14658 RingCT/type: yes/0
Extra: 0129dd851e82d8ae66e4835f6bbbf807f0d4e627fb06b642f11e2851090c5986c10211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1f0c428d5253d4f076d5d541c7534986f5626c5dafbb1f152bb800b47cf3c31 0.600000000000 1617639 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": 1134356, "vin": [ { "gen": { "height": 1134346 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1f0c428d5253d4f076d5d541c7534986f5626c5dafbb1f152bb800b47cf3c31" } } ], "extra": [ 1, 41, 221, 133, 30, 130, 216, 174, 102, 228, 131, 95, 107, 187, 248, 7, 240, 212, 230, 39, 251, 6, 182, 66, 241, 30, 40, 81, 9, 12, 89, 134, 193, 2, 17, 0, 0, 0, 2, 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