Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 067ab1d3d62d9935cae51604788bdbdae3d0c3c882d8787e721550879acde2c1

Tx prefix hash: dd7338d03e972d589fce9d6a68818cc5019b460ab8689908bea2bc7cbce86db2
Tx public key: c67822cfaf5f0dfb64463fb23495a4aaf4addbfb5d49b91c9380fa55b73026f4
Timestamp: 1736774026 Timestamp [UCT]: 2025-01-13 13:13:46 Age [y:d:h:m:s]: 00:155:23:11:51
Block: 1196481 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111176 RingCT/type: yes/0
Extra: 01c67822cfaf5f0dfb64463fb23495a4aaf4addbfb5d49b91c9380fa55b73026f402110000001a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8cb4c36c77ef39a4996c714c57810735d4f03075889f0d4b06b28195a49de2e0 0.600000000000 1683080 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": 1196491, "vin": [ { "gen": { "height": 1196481 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8cb4c36c77ef39a4996c714c57810735d4f03075889f0d4b06b28195a49de2e0" } } ], "extra": [ 1, 198, 120, 34, 207, 175, 95, 13, 251, 100, 70, 63, 178, 52, 149, 164, 170, 244, 173, 219, 251, 93, 73, 185, 28, 147, 128, 250, 85, 183, 48, 38, 244, 2, 17, 0, 0, 0, 26, 0, 127, 151, 138, 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