Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c64c40ecc85c99dbc3acc29c0ddcc6783eed320ed79e6e7425ff45a532b3e1d4

Tx prefix hash: d4211b357a69481f4d44c1eb9645f08216e64a95c11f0b5f5d164e3683b4eeb2
Tx public key: 3ab4fc0d113e69e54742c79e61ada3c0c317dce0474915ba9046db46226a784d
Timestamp: 1743798531 Timestamp [UTC]: 2025-04-04 20:28:51 Age [y:d:h:m:s]: 01:141:12:07:50
Block: 1254351 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365472 RingCT/type: yes/0
Extra: 013ab4fc0d113e69e54742c79e61ada3c0c317dce0474915ba9046db46226a784d0211000000094060f6d2000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1ad2c9110564c49399d1f2f82e4984cfb61a7190f0e1538409b08b12445f6e83 0.000600000000 1741432 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": 1254361, "vin": [ { "gen": { "height": 1254351 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1ad2c9110564c49399d1f2f82e4984cfb61a7190f0e1538409b08b12445f6e83" } } ], "extra": [ 1, 58, 180, 252, 13, 17, 62, 105, 229, 71, 66, 199, 158, 97, 173, 163, 192, 195, 23, 220, 224, 71, 73, 21, 186, 144, 70, 219, 70, 34, 106, 120, 77, 2, 17, 0, 0, 0, 9, 64, 96, 246, 210, 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: