Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e785490c91d1b1fc6fc9dc7a136383f68cd46b996e85be7f985ac914d9b6920e

Tx prefix hash: 76c80448979978f1f1ec714901f4a460e08c8ff269d981fb8be9ea464019788b
Tx public key: bd04fc93959313bb0f2618d948c793e102c31fa1d88b24f34c9ed452b8935358
Timestamp: 1728727162 Timestamp [UCT]: 2024-10-12 09:59:22 Age [y:d:h:m:s]: 01:029:11:05:43
Block: 1129909 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279428 RingCT/type: yes/0
Extra: 01bd04fc93959313bb0f2618d948c793e102c31fa1d88b24f34c9ed452b893535802110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9b6579273f93bf1c9d9b89c95054e8655f8ce9f9b5bb7c3b45745c8687e5a7f 0.600000000000 1612780 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": 1129919, "vin": [ { "gen": { "height": 1129909 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9b6579273f93bf1c9d9b89c95054e8655f8ce9f9b5bb7c3b45745c8687e5a7f" } } ], "extra": [ 1, 189, 4, 252, 147, 149, 147, 19, 187, 15, 38, 24, 217, 72, 199, 147, 225, 2, 195, 31, 161, 216, 139, 36, 243, 76, 158, 212, 82, 184, 147, 83, 88, 2, 17, 0, 0, 0, 2, 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