Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4a8cb3dfe6a481555e5d0f5aa594bebf339d73ab31850b55d52b4af69a54770

Tx prefix hash: d4fbffceb5f0a3c33329a30c64394cc2f708e24e1951c8b528635895378a61a5
Tx public key: 7b05228369fe43dc50d76464e90fd1cf1e9d17ba81aac612c2fdd5d75466d766
Timestamp: 1709599943 Timestamp [UCT]: 2024-03-05 00:52:23 Age [y:d:h:m:s]: 01:250:23:51:27
Block: 971345 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 438101 RingCT/type: yes/0
Extra: 017b05228369fe43dc50d76464e90fd1cf1e9d17ba81aac612c2fdd5d75466d76602110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 811c8ff50dd060c1fb38175941337a2f1356ce2ae71b63dccdc2e067e8cf0855 0.600000000000 1431240 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": 971355, "vin": [ { "gen": { "height": 971345 } } ], "vout": [ { "amount": 600000000, "target": { "key": "811c8ff50dd060c1fb38175941337a2f1356ce2ae71b63dccdc2e067e8cf0855" } } ], "extra": [ 1, 123, 5, 34, 131, 105, 254, 67, 220, 80, 215, 100, 100, 233, 15, 209, 207, 30, 157, 23, 186, 129, 170, 198, 18, 194, 253, 213, 215, 84, 102, 215, 102, 2, 17, 0, 0, 0, 6, 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