Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1a977d79a40d3342ca28fcef7ad67d25ff05417aff213e3518fa2355447c4d6

Tx prefix hash: b78dc5cf54dd68da69c259c9023e2210022512077af8cb244e14466985e0411d
Tx public key: 65f743a259b5f7f9e7f8b9be037a5810fe74281ca791330e2b85d5c5ec8223d6
Timestamp: 1636974970 Timestamp [UTC]: 2021-11-15 11:16:10 Age [y:d:h:m:s]: 05:008:05:07:13
Block: 374783 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1308711 RingCT/type: yes/0
Extra: 0165f743a259b5f7f9e7f8b9be037a5810fe74281ca791330e2b85d5c5ec8223d60211000000014a0f5013000000000000000000

1 output(s) for total of 0.035171934901 xmr

stealth address amount amount idx tag
00: 3ff3521c71c954c3cd7db03c059d5a1878f7b4d39c8e9741aa5dbc4394dc748b 0.035171934901 758519 of 0 -

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": 374793, "vin": [ { "gen": { "height": 374783 } } ], "vout": [ { "amount": 35171934901, "target": { "key": "3ff3521c71c954c3cd7db03c059d5a1878f7b4d39c8e9741aa5dbc4394dc748b" } } ], "extra": [ 1, 101, 247, 67, 162, 89, 181, 247, 249, 231, 248, 185, 190, 3, 122, 88, 16, 254, 116, 40, 28, 167, 145, 51, 14, 43, 133, 213, 197, 236, 130, 35, 214, 2, 17, 0, 0, 0, 1, 74, 15, 80, 19, 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: