Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fdbd763c8438bca1f4618b19cd1aec287dca62fae1eb9eed0fc6a788d27e6fa0

Tx prefix hash: 1fb98207fa81cdcc2e4217c141d36ade862dd16a000154b18dc426de83b2ff1f
Tx public key: 0406bdb303755ecad4a1c7ba055e8b7fc0942420e9e70777f8ad002af319bd3a
Timestamp: 1772771384 Timestamp [UTC]: 2026-03-06 04:29:44 Age [y:d:h:m:s]: 00:260:06:16:47
Block: 1491691 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191669 RingCT/type: yes/0
Extra: 010406bdb303755ecad4a1c7ba055e8b7fc0942420e9e70777f8ad002af319bd3a021100000005e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 66dceabe8512aa84eac8d831f611d2432227b6d7ace6958ee533eae174911c61 0.000600000000 1981211 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": 1491701, "vin": [ { "gen": { "height": 1491691 } } ], "vout": [ { "amount": 600000000, "target": { "key": "66dceabe8512aa84eac8d831f611d2432227b6d7ace6958ee533eae174911c61" } } ], "extra": [ 1, 4, 6, 189, 179, 3, 117, 94, 202, 212, 161, 199, 186, 5, 94, 139, 127, 192, 148, 36, 32, 233, 231, 7, 119, 248, 173, 0, 42, 243, 25, 189, 58, 2, 17, 0, 0, 0, 5, 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: