Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f433700cf0d6a9a7faebf19230ac9adc0d1efbc1817a7676b26a20665083e16

Tx prefix hash: 003d7cd0277a1629e2bca3e53487f9cc29d67da9de618036f58b85ff9c0364e8
Tx public key: 89c84f3acc060d6f8fd53e87ee01409615a40562668a53b3a621ae5449643aec
Timestamp: 1745463631 Timestamp [UCT]: 2025-04-24 03:00:31 Age [y:d:h:m:s]: 00:211:04:44:19
Block: 1268142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148657 RingCT/type: yes/0
Extra: 0189c84f3acc060d6f8fd53e87ee01409615a40562668a53b3a621ae5449643aec021100000003d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 512043336aa67d0a0e3a96548c44beda277fee3e1594eefdb95ba97ed11f26f3 0.600000000000 1755371 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": 1268152, "vin": [ { "gen": { "height": 1268142 } } ], "vout": [ { "amount": 600000000, "target": { "key": "512043336aa67d0a0e3a96548c44beda277fee3e1594eefdb95ba97ed11f26f3" } } ], "extra": [ 1, 137, 200, 79, 58, 204, 6, 13, 111, 143, 213, 62, 135, 238, 1, 64, 150, 21, 164, 5, 98, 102, 138, 83, 179, 166, 33, 174, 84, 73, 100, 58, 236, 2, 17, 0, 0, 0, 3, 216, 231, 210, 65, 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