Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60a65d0167d4b4191032ce6a41eba43f5c7668083fe2d4411ae5ec65eeba510b

Tx prefix hash: 3e2091a73b4e95bd4ffcd718d40e6d76561ff8de29a039cbe7a81ca89de19ecb
Tx public key: 60723ea2a9fa9ca4779a1fb8adb68c1df66e951c1a437c75323eb491d8779f53
Timestamp: 1738056456 Timestamp [UCT]: 2025-01-28 09:27:36 Age [y:d:h:m:s]: 00:329:16:21:32
Block: 1206848 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233410 RingCT/type: yes/0
Extra: 0160723ea2a9fa9ca4779a1fb8adb68c1df66e951c1a437c75323eb491d8779f53021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: faf6398e66a636f8f6da644343fa4d2e6cf408372d73ba84453c74ca5488b310 0.600000000000 1693561 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": 1206858, "vin": [ { "gen": { "height": 1206848 } } ], "vout": [ { "amount": 600000000, "target": { "key": "faf6398e66a636f8f6da644343fa4d2e6cf408372d73ba84453c74ca5488b310" } } ], "extra": [ 1, 96, 114, 62, 162, 169, 250, 156, 164, 119, 154, 31, 184, 173, 182, 140, 29, 246, 110, 149, 28, 26, 67, 124, 117, 50, 62, 180, 145, 216, 119, 159, 83, 2, 17, 0, 0, 0, 3, 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