Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04d9cc4a50869ecd93dfc52fda0e16f434c43160ad5b2dd98b6566d6f2026484

Tx prefix hash: c2b3af9535c7e0c56b5b6c23a004e84b251207304deb0ce3f8d09e35aca1fdd9
Tx public key: d6b667d991568968753eafee57dbc05574af2c1624d844cf57ae8598a5d0a303
Timestamp: 1746002224 Timestamp [UCT]: 2025-04-30 08:37:04 Age [y:d:h:m:s]: 00:203:17:39:22
Block: 1272628 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143311 RingCT/type: yes/0
Extra: 01d6b667d991568968753eafee57dbc05574af2c1624d844cf57ae8598a5d0a303021100000008d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 18ebfe680b11fc1aecac57794033a6b267e73beb35b0c2d9c68cb0b1b6e4479e 0.600000000000 1759903 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": 1272638, "vin": [ { "gen": { "height": 1272628 } } ], "vout": [ { "amount": 600000000, "target": { "key": "18ebfe680b11fc1aecac57794033a6b267e73beb35b0c2d9c68cb0b1b6e4479e" } } ], "extra": [ 1, 214, 182, 103, 217, 145, 86, 137, 104, 117, 62, 175, 238, 87, 219, 192, 85, 116, 175, 44, 22, 36, 216, 68, 207, 87, 174, 133, 152, 165, 208, 163, 3, 2, 17, 0, 0, 0, 8, 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