Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5fda4b1c4c54c3ece5167e0b5f438243d212f6ba30c916e3280bdfeeb656be0

Tx prefix hash: 3d1ea1ecb42d9ca27c2c14357e94ba6b45171fd4e1802639cb62935a1df2cb53
Tx public key: ebd2c045cf680d3912a6568304b5cc10c49626bf18087cba9b0dd5fee5b3e225
Timestamp: 1710671921 Timestamp [UTC]: 2024-03-17 10:38:41 Age [y:d:h:m:s]: 02:247:10:38:41
Block: 980240 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 701923 RingCT/type: yes/0
Extra: 01ebd2c045cf680d3912a6568304b5cc10c49626bf18087cba9b0dd5fee5b3e22502110000000359dad3f5000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 78d427fb5c417ac1ecf14a8ed2582ccde52822b09904b15b7c9e5e55061661f4 0.000600000000 1440305 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": 980250, "vin": [ { "gen": { "height": 980240 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78d427fb5c417ac1ecf14a8ed2582ccde52822b09904b15b7c9e5e55061661f4" } } ], "extra": [ 1, 235, 210, 192, 69, 207, 104, 13, 57, 18, 166, 86, 131, 4, 181, 204, 16, 196, 150, 38, 191, 24, 8, 124, 186, 155, 13, 213, 254, 229, 179, 226, 37, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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: