Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4f278c8707c61089c3ba5ab543342cf8bfe38b4227e076add41c8b658fb9caf

Tx prefix hash: 258094b5639d0fb84aa08b9f061361c99bd8d3cd72694fb7c8a28e131a7c97dd
Tx public key: e9918320e80ac2fed9c3fbbfcb399cf63e0f89becf7ca273b6cace3f87d5d775
Timestamp: 1726090843 Timestamp [UCT]: 2024-09-11 21:40:43 Age [y:d:h:m:s]: 00:117:12:29:00
Block: 1108045 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 84050 RingCT/type: yes/0
Extra: 01e9918320e80ac2fed9c3fbbfcb399cf63e0f89becf7ca273b6cace3f87d5d77502110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b06392c85d435437d46162605917955f034c6098700029a7a0e8098f8e5d2e54 0.600000000000 1585806 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": 1108055, "vin": [ { "gen": { "height": 1108045 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b06392c85d435437d46162605917955f034c6098700029a7a0e8098f8e5d2e54" } } ], "extra": [ 1, 233, 145, 131, 32, 232, 10, 194, 254, 217, 195, 251, 191, 203, 57, 156, 246, 62, 15, 137, 190, 207, 124, 162, 115, 182, 202, 206, 63, 135, 213, 215, 117, 2, 17, 0, 0, 0, 9, 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