Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9aba1715fa1a339387dd64f4aee7a743e18b1cd49ee996ed5ff8695a51f2a21

Tx prefix hash: 64ef7a76c49dd44217fd1430fce88cc6b9965a02215f6b83ee8c3b9b0fb70020
Tx public key: a15e1a00e5dac4156688c9f545a0272f6f3d4ab32f5210ec454081a55515f3d7
Timestamp: 1723955834 Timestamp [UCT]: 2024-08-18 04:37:14 Age [y:d:h:m:s]: 00:234:13:56:22
Block: 1090360 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167518 RingCT/type: yes/0
Extra: 01a15e1a00e5dac4156688c9f545a0272f6f3d4ab32f5210ec454081a55515f3d702110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a5b2064fad58045fa0cf495c19342c23107e26bae4ff1808dc4f76ccca6d8bd8 0.600000000000 1564983 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": 1090370, "vin": [ { "gen": { "height": 1090360 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a5b2064fad58045fa0cf495c19342c23107e26bae4ff1808dc4f76ccca6d8bd8" } } ], "extra": [ 1, 161, 94, 26, 0, 229, 218, 196, 21, 102, 136, 201, 245, 69, 160, 39, 47, 111, 61, 74, 179, 47, 82, 16, 236, 69, 64, 129, 165, 85, 21, 243, 215, 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