Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8b5c9c854bc5d0b7c193be176a64768d12b89f54e6d290b55ab07f1b885e04df

Tx prefix hash: c0aac212b0ce1d6b66669cb34e736f77751fa35c1ac5044ca5a419f6286802a5
Tx public key: 06006e06e75ac244640dec5f7e524b5365681c5fdb6d624e4ca8809595fce2e8
Timestamp: 1736804312 Timestamp [UCT]: 2025-01-13 21:38:32 Age [y:d:h:m:s]: 00:159:15:19:20
Block: 1196727 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113725 RingCT/type: yes/0
Extra: 0106006e06e75ac244640dec5f7e524b5365681c5fdb6d624e4ca8809595fce2e80211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ac9f3c38475a84ae3d978f815ee0e4a7543642cc904d53e512a871beee69509 0.600000000000 1683330 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": 1196737, "vin": [ { "gen": { "height": 1196727 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ac9f3c38475a84ae3d978f815ee0e4a7543642cc904d53e512a871beee69509" } } ], "extra": [ 1, 6, 0, 110, 6, 231, 90, 194, 68, 100, 13, 236, 95, 126, 82, 75, 83, 101, 104, 28, 95, 219, 109, 98, 78, 76, 168, 128, 149, 149, 252, 226, 232, 2, 17, 0, 0, 0, 3, 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