Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc7a4d587c0fe37041e4dd6642aafe4f78f6e05f1a68c413922135919beb431d

Tx prefix hash: 606e1a5228d8afd460c29681099aad957e4011767c0536411eb1bc99a16962cb
Tx public key: 325f4d555cc8e24fa945ad6181b23aa8e5fae0ca7ee39f0eeeb5a84343d3eeea
Timestamp: 1713784917 Timestamp [UCT]: 2024-04-22 11:21:57 Age [y:d:h:m:s]: 00:186:05:03:15
Block: 1006027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133345 RingCT/type: yes/0
Extra: 01325f4d555cc8e24fa945ad6181b23aa8e5fae0ca7ee39f0eeeb5a84343d3eeea02110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7af1da2618dbcc7a97f5d20685c694605450272fcae96df9166179b6873760d 0.600000000000 1466915 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": 1006037, "vin": [ { "gen": { "height": 1006027 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7af1da2618dbcc7a97f5d20685c694605450272fcae96df9166179b6873760d" } } ], "extra": [ 1, 50, 95, 77, 85, 92, 200, 226, 79, 169, 69, 173, 97, 129, 178, 58, 168, 229, 250, 224, 202, 126, 227, 159, 14, 238, 181, 168, 67, 67, 211, 238, 234, 2, 17, 0, 0, 0, 9, 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