Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bb2fba3400e1a2625a3243480c212f15d147e5187bf094a21ec0f45ece59f25f

Tx prefix hash: 150afc76be365fd40be5352819932435a4c80eee225def9fcaa3a5a209558573
Tx public key: 7f159d2e180ce1f8c8909de0e891020a9fc226e059be1b0d6c82e6e805683848
Timestamp: 1636854959 Timestamp [UTC]: 2021-11-14 01:55:59 Age [y:d:h:m:s]: 05:006:17:54:25
Block: 373887 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1308227 RingCT/type: yes/0
Extra: 017f159d2e180ce1f8c8909de0e891020a9fc226e059be1b0d6c82e6e80568384802110000002006faf294000000000000000000

1 output(s) for total of 0.035412578457 xmr

stealth address amount amount idx tag
00: 31df931f9040125021c241e9f50f83fb415db611075a62c37be4a0e94e0fb97b 0.035412578457 756975 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": 373897, "vin": [ { "gen": { "height": 373887 } } ], "vout": [ { "amount": 35412578457, "target": { "key": "31df931f9040125021c241e9f50f83fb415db611075a62c37be4a0e94e0fb97b" } } ], "extra": [ 1, 127, 21, 157, 46, 24, 12, 225, 248, 200, 144, 157, 224, 232, 145, 2, 10, 159, 194, 38, 224, 89, 190, 27, 13, 108, 130, 230, 232, 5, 104, 56, 72, 2, 17, 0, 0, 0, 32, 6, 250, 242, 148, 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: