Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf7afaf8ed83054059e595b7cc7748df02b056dab2b2922281dcdf1f8b54d95c

Tx prefix hash: d92ce72d506ef7ac4425ab3adc2c42747885357004490658d04104df909f6133
Tx public key: 6949d693fb76bcb3fbccb3698057e360af413c92fa94c82b70435b0034e804d5
Timestamp: 1730296052 Timestamp [UTC]: 2024-10-30 13:47:32 Age [y:d:h:m:s]: 01:196:18:27:55
Block: 1142839 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391398 RingCT/type: yes/0
Extra: 016949d693fb76bcb3fbccb3698057e360af413c92fa94c82b70435b0034e804d50211000000018368266d000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b80da8ef9f472fbc651c6c9c6f3a5ed915416f70d39a91c17dcebcf01d581391 0.000600000000 1626694 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": 1142849, "vin": [ { "gen": { "height": 1142839 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b80da8ef9f472fbc651c6c9c6f3a5ed915416f70d39a91c17dcebcf01d581391" } } ], "extra": [ 1, 105, 73, 214, 147, 251, 118, 188, 179, 251, 204, 179, 105, 128, 87, 227, 96, 175, 65, 60, 146, 250, 148, 200, 43, 112, 67, 91, 0, 52, 232, 4, 213, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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: