Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bef0b5f5d527fc1b32b3fd019f42a60e0dfa4417030e7df2e6f5859a9843787d

Tx prefix hash: 380e0c92bf10a374dd31acda0b67c2c149bbbba4274e3df85dae9c1eec9ec98c
Tx public key: 8b7e84746b36197cf8df73de7efbe07d76ad784d42f3af83875f8be105f36760
Timestamp: 1745762013 Timestamp [UTC]: 2025-04-27 13:53:33 Age [y:d:h:m:s]: 01:206:01:03:05
Block: 1270627 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 411330 RingCT/type: yes/0
Extra: 018b7e84746b36197cf8df73de7efbe07d76ad784d42f3af83875f8be105f367600211000000012609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: a497d73bd91f3e81402fb8d32ed8751c6124b60280dd9850da91c342f725cecc 0.000600000000 1757870 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": 1270637, "vin": [ { "gen": { "height": 1270627 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a497d73bd91f3e81402fb8d32ed8751c6124b60280dd9850da91c342f725cecc" } } ], "extra": [ 1, 139, 126, 132, 116, 107, 54, 25, 124, 248, 223, 115, 222, 126, 251, 224, 125, 118, 173, 120, 77, 66, 243, 175, 131, 135, 95, 139, 225, 5, 243, 103, 96, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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: