Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bbb922e7d87583af9250cec08ebbea47f5e82c442f4225e263fafe925265b1e3

Tx prefix hash: 9e602a0417d812840b966c0ab665be6a26ce71bc7414467966df2d851d1292a9
Tx public key: 1df4f066eb8112013b9b3d58db7917adadf5f12c34bf18fad6bb096c5e5c1083
Timestamp: 1735595125 Timestamp [UCT]: 2024-12-30 21:45:25 Age [y:d:h:m:s]: 00:099:03:13:15
Block: 1186715 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70641 RingCT/type: yes/0
Extra: 011df4f066eb8112013b9b3d58db7917adadf5f12c34bf18fad6bb096c5e5c1083021100000009e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 02df666ac5428adec9988466739b2c26a7f80c440e19bc13be2d803816ea0d79 0.600000000000 1673200 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": 1186725, "vin": [ { "gen": { "height": 1186715 } } ], "vout": [ { "amount": 600000000, "target": { "key": "02df666ac5428adec9988466739b2c26a7f80c440e19bc13be2d803816ea0d79" } } ], "extra": [ 1, 29, 244, 240, 102, 235, 129, 18, 1, 59, 155, 61, 88, 219, 121, 23, 173, 173, 245, 241, 44, 52, 191, 24, 250, 214, 187, 9, 108, 94, 92, 16, 131, 2, 17, 0, 0, 0, 9, 228, 220, 144, 9, 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