Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4029e027a1d43f5698c7e474b9c2d212eaf9cfc3a2662aaeb45d356bed4ae5f

Tx prefix hash: b54a376eff2af2ea24ed69adb3a509355b517753fc34d070803e932407f47d17
Tx public key: 217e048d81f8e1f20b95f2582bd3fb79486e674df42b515ecf76daae7a9aa42d
Timestamp: 1725524332 Timestamp [UCT]: 2024-09-05 08:18:52 Age [y:d:h:m:s]: 00:219:08:21:50
Block: 1103356 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156614 RingCT/type: yes/0
Extra: 01217e048d81f8e1f20b95f2582bd3fb79486e674df42b515ecf76daae7a9aa42d021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8f8ceca7257c6ed375818b3b03c3b73f7f7fd4b823ff01da529fe97ead5ab868 0.600000000000 1580151 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": 1103366, "vin": [ { "gen": { "height": 1103356 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8f8ceca7257c6ed375818b3b03c3b73f7f7fd4b823ff01da529fe97ead5ab868" } } ], "extra": [ 1, 33, 126, 4, 141, 129, 248, 225, 242, 11, 149, 242, 88, 43, 211, 251, 121, 72, 110, 103, 77, 244, 43, 81, 94, 207, 118, 218, 174, 122, 154, 164, 45, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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