Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bba887d3135a07cdc5d9bf5c59986d7f3fe42f405c9afc878cf1ec87bfca4ed0

Tx prefix hash: 28d7fa8e2425d2a56ec2a9874e272d1b06c4051a8f1d0fb998e33af21a1c5533
Tx public key: 6d05304b9d56d7aeb8d88ba88c7020e937190314ba0197dfc06e7bc9dd7fd433
Timestamp: 1769755554 Timestamp [UTC]: 2026-01-30 06:45:54 Age [y:d:h:m:s]: 00:288:04:36:17
Block: 1466728 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211381 RingCT/type: yes/0
Extra: 016d05304b9d56d7aeb8d88ba88c7020e937190314ba0197dfc06e7bc9dd7fd43302110000000949d73e98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 8aeed0b42b8e2b610b95c8b3e2e58392034df590ac0f36daad0a19117c089014 0.000600000000 1955964 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": 1466738, "vin": [ { "gen": { "height": 1466728 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8aeed0b42b8e2b610b95c8b3e2e58392034df590ac0f36daad0a19117c089014" } } ], "extra": [ 1, 109, 5, 48, 75, 157, 86, 215, 174, 184, 216, 139, 168, 140, 112, 32, 233, 55, 25, 3, 20, 186, 1, 151, 223, 192, 110, 123, 201, 221, 127, 212, 51, 2, 17, 0, 0, 0, 9, 73, 215, 62, 152, 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: