Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c806f7b23eeca426ea48e390b7d326500372eb7faae75b1e354f3d01f040edca

Tx prefix hash: 1b63699789210ef184fbd16ad5b0110f9fc4bc9b251b9e2d94d75f41031284dd
Tx public key: 1dd2ad9ab2987f236793813aef9ae11a90d386220e4613a165dc6d886c7b7f7e
Timestamp: 1762551351 Timestamp [UCT]: 2025-11-07 21:35:51 Age [y:d:h:m:s]: 00:046:02:41:30
Block: 1407206 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33009 RingCT/type: yes/0
Extra: 011dd2ad9ab2987f236793813aef9ae11a90d386220e4613a165dc6d886c7b7f7e02110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d0d148234a997bb9406d8421ccc2f9280729f4c223646f201bda3e6a2c93709 0.600000000000 1895617 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": 1407216, "vin": [ { "gen": { "height": 1407206 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d0d148234a997bb9406d8421ccc2f9280729f4c223646f201bda3e6a2c93709" } } ], "extra": [ 1, 29, 210, 173, 154, 178, 152, 127, 35, 103, 147, 129, 58, 239, 154, 225, 26, 144, 211, 134, 34, 14, 70, 19, 161, 101, 220, 109, 136, 108, 123, 127, 126, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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