Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ccb70f696a6fb3ef0396a3e19664d4c3149076adb786153cb5786eed1b58d34

Tx prefix hash: 01bdcc5d231e2e4f2922001e1e08648ff6111bf720341cdf3fbb6b15571a2fb5
Tx public key: 6aaeebe5d3c533f6a2ca989f19ca9f97488afb22739d501be35192a480b25c6e
Timestamp: 1737351439 Timestamp [UCT]: 2025-01-20 05:37:19 Age [y:d:h:m:s]: 00:148:16:14:31
Block: 1201219 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105992 RingCT/type: yes/0
Extra: 016aaeebe5d3c533f6a2ca989f19ca9f97488afb22739d501be35192a480b25c6e0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 86f23ea3c385763bbbd8badd592be8b919ae8d2f238656eb1a7e1d4a46cac33a 0.600000000000 1687868 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": 1201229, "vin": [ { "gen": { "height": 1201219 } } ], "vout": [ { "amount": 600000000, "target": { "key": "86f23ea3c385763bbbd8badd592be8b919ae8d2f238656eb1a7e1d4a46cac33a" } } ], "extra": [ 1, 106, 174, 235, 229, 211, 197, 51, 246, 162, 202, 152, 159, 25, 202, 159, 151, 72, 138, 251, 34, 115, 157, 80, 27, 227, 81, 146, 164, 128, 178, 92, 110, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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