Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bdfdcebd29d17302773f87722f57704fca8d9f2f2448d3cfd52128828055b65c

Tx prefix hash: 0b0b8d2fa3414900ec2bbea0cdc8e9ad2f65f6ba935c9e050e778b8794e371a0
Tx public key: cf5a843a7185d54b203bb471df0404b1799af20e35344c80999920cca24fd7c8
Timestamp: 1747824337 Timestamp [UTC]: 2025-05-21 10:45:37 Age [y:d:h:m:s]: 01:184:04:19:10
Block: 1287699 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 395788 RingCT/type: yes/0
Extra: 01cf5a843a7185d54b203bb471df0404b1799af20e35344c80999920cca24fd7c80211000000079f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 076630ea00619759c09a12fc77db698cc6778bf8af323d7adaf8ae5bfca0b81b 0.000600000000 1775166 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": 1287709, "vin": [ { "gen": { "height": 1287699 } } ], "vout": [ { "amount": 600000000, "target": { "key": "076630ea00619759c09a12fc77db698cc6778bf8af323d7adaf8ae5bfca0b81b" } } ], "extra": [ 1, 207, 90, 132, 58, 113, 133, 213, 75, 32, 59, 180, 113, 223, 4, 4, 177, 121, 154, 242, 14, 53, 52, 76, 128, 153, 153, 32, 204, 162, 79, 215, 200, 2, 17, 0, 0, 0, 7, 159, 159, 230, 140, 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: