Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e3709709328d2702be4dcad4089428989c303ae494c6142e2d0ee77d46a4c8e

Tx prefix hash: 12e41aee7b78abcf8480fd44b7a6238108dc7b3e1eee1c7f223e248adf523977
Tx public key: 95861f423968749c7a0527b2bedc4d8502e439e8cf1bd498aabf0afee5b9a1e8
Timestamp: 1728777869 Timestamp [UCT]: 2024-10-13 00:04:29 Age [y:d:h:m:s]: 00:169:05:33:24
Block: 1130335 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120720 RingCT/type: yes/0
Extra: 0195861f423968749c7a0527b2bedc4d8502e439e8cf1bd498aabf0afee5b9a1e802110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fcec0aa55bb36dadbdf1dc69ab08b5e5553bcd6e1a735c31b6f26da947679c9d 0.600000000000 1613210 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": 1130345, "vin": [ { "gen": { "height": 1130335 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fcec0aa55bb36dadbdf1dc69ab08b5e5553bcd6e1a735c31b6f26da947679c9d" } } ], "extra": [ 1, 149, 134, 31, 66, 57, 104, 116, 156, 122, 5, 39, 178, 190, 220, 77, 133, 2, 228, 57, 232, 207, 27, 212, 152, 170, 191, 10, 254, 229, 185, 161, 232, 2, 17, 0, 0, 0, 1, 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