Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6af53a5e18a0c40b4de9426303de42ddef0c267a05374d52113d3484c2ab7963

Tx prefix hash: 17d50076278dc0e437eb308c71ad9516120871939444f0af470dbd8020503ccb
Tx public key: 0bba987f13e3a16f0a2734ea731f2b75ed2a2a579511381c52b9b02e83c513b8
Timestamp: 1696348843 Timestamp [UCT]: 2023-10-03 16:00:43 Age [y:d:h:m:s]: 01:182:07:41:03
Block: 861679 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391333 RingCT/type: yes/0
Extra: 010bba987f13e3a16f0a2734ea731f2b75ed2a2a579511381c52b9b02e83c513b80211000000024b8f5122000000000000000000

1 output(s) for total of 0.856840158000 dcy

stealth address amount amount idx
00: b028cc397cea56c452924c7d049e110d5fe88dd84d23761b99d923c37a270c2e 0.856840158000 1316041 of 0

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": 861689, "vin": [ { "gen": { "height": 861679 } } ], "vout": [ { "amount": 856840158, "target": { "key": "b028cc397cea56c452924c7d049e110d5fe88dd84d23761b99d923c37a270c2e" } } ], "extra": [ 1, 11, 186, 152, 127, 19, 227, 161, 111, 10, 39, 52, 234, 115, 31, 43, 117, 237, 42, 42, 87, 149, 17, 56, 28, 82, 185, 176, 46, 131, 197, 19, 184, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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