Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5be468c59c71076ad25139339b40c68da698770b45be151c96bfcb8b0ae9a74

Tx prefix hash: 2abec31096fa90a6b13411f2e65288ed9131757a94fdd79a842e73ce2a5670fb
Tx public key: 30cd3f4a8b1710197d8a5c849c45a75956941b17fde495b2e8296ebf74fab58c
Timestamp: 1712435193 Timestamp [UCT]: 2024-04-06 20:26:33 Age [y:d:h:m:s]: 01:051:12:48:51
Block: 994811 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 297856 RingCT/type: yes/0
Extra: 0130cd3f4a8b1710197d8a5c849c45a75956941b17fde495b2e8296ebf74fab58c02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a9e8e86751e8c403879215fb4ba0f4021ea07fb4a4e51d6ac8061df9c8d4be0 0.600000000000 1455215 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": 994821, "vin": [ { "gen": { "height": 994811 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a9e8e86751e8c403879215fb4ba0f4021ea07fb4a4e51d6ac8061df9c8d4be0" } } ], "extra": [ 1, 48, 205, 63, 74, 139, 23, 16, 25, 125, 138, 92, 132, 156, 69, 167, 89, 86, 148, 27, 23, 253, 228, 149, 178, 232, 41, 110, 191, 116, 250, 181, 140, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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