Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 47c58e7ff9f651f5e035e34738b7a87c842ce0bd03253d2f4b98fa13978d74eb

Tx prefix hash: ac6d95773413658079c870af5b8c59d9f117229bd8a3de873596de8a7f0c9413
Tx public key: f52a328369af7d413acbbe32740775221e5f6108c61e5922e0550d4af0b83f32
Timestamp: 1734553525 Timestamp [UCT]: 2024-12-18 20:25:25 Age [y:d:h:m:s]: 00:106:09:38:18
Block: 1178135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75799 RingCT/type: yes/0
Extra: 01f52a328369af7d413acbbe32740775221e5f6108c61e5922e0550d4af0b83f320211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ab599db9c172f5ea0f8ba41b7a88c2dc4827baf40b5033c282b3ff8f31c8120 0.600000000000 1664518 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": 1178145, "vin": [ { "gen": { "height": 1178135 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ab599db9c172f5ea0f8ba41b7a88c2dc4827baf40b5033c282b3ff8f31c8120" } } ], "extra": [ 1, 245, 42, 50, 131, 105, 175, 125, 65, 58, 203, 190, 50, 116, 7, 117, 34, 30, 95, 97, 8, 198, 30, 89, 34, 224, 85, 13, 74, 240, 184, 63, 50, 2, 17, 0, 0, 0, 1, 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