Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20fdeb9de27bc4ac2b24be5e3eafa0091c9d5ecf0165a9d4cb4b129ddf2c5779

Tx prefix hash: 8c8a8e47c899dc3011a529855818242359c0ad9d51dd9a5dd8959e387b088d7b
Tx public key: b4a8664e80a356235fce5379f74a96c449648583fdca0a8fb878a0200147357f
Timestamp: 1741338358 Timestamp [UTC]: 2025-03-07 09:05:58 Age [y:d:h:m:s]: 01:258:18:16:28
Block: 1233997 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 449133 RingCT/type: yes/0
Extra: 01b4a8664e80a356235fce5379f74a96c449648583fdca0a8fb878a0200147357f02110000000b1f0a53eb000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1521314007c7a1b9a5fbf3a8b4c9edc85a2ecb1983f4363aa570edef5f88a4f3 0.000600000000 1720922 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 dinastycoin-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": 1234007, "vin": [ { "gen": { "height": 1233997 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1521314007c7a1b9a5fbf3a8b4c9edc85a2ecb1983f4363aa570edef5f88a4f3" } } ], "extra": [ 1, 180, 168, 102, 78, 128, 163, 86, 35, 95, 206, 83, 121, 247, 74, 150, 196, 73, 100, 133, 131, 253, 202, 10, 143, 184, 120, 160, 32, 1, 71, 53, 127, 2, 17, 0, 0, 0, 11, 31, 10, 83, 235, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: