Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb921947c8aad416ebbc3e368c58a2a018a0599524f9c78253d848e0c52083fc

Tx prefix hash: cbd0e24f28aabe952524e31e592dfcfcf131cd9652b8331be16dbf9e1f8414c8
Tx public key: 5e74e230e6be242b5faebc79b861fbfd7b14b850486928a380eb3dd20c9b69f2
Timestamp: 1772386020 Timestamp [UTC]: 2026-03-01 17:27:00 Age [y:d:h:m:s]: 00:262:09:17:23
Block: 1488498 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193080 RingCT/type: yes/0
Extra: 015e74e230e6be242b5faebc79b861fbfd7b14b850486928a380eb3dd20c9b69f2021100000008e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: af433abde97cea37402b364c82861e84b55a9465c0b9c4124f22862804728d97 0.000600000000 1977976 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": 1488508, "vin": [ { "gen": { "height": 1488498 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af433abde97cea37402b364c82861e84b55a9465c0b9c4124f22862804728d97" } } ], "extra": [ 1, 94, 116, 226, 48, 230, 190, 36, 43, 95, 174, 188, 121, 184, 97, 251, 253, 123, 20, 184, 80, 72, 105, 40, 163, 128, 235, 61, 210, 12, 155, 105, 242, 2, 17, 0, 0, 0, 8, 228, 245, 25, 63, 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: