Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05e4984d47fc43d53fa4d4d216db5c61420c6e9773548cc1bc79f7ae7059a0b7

Tx prefix hash: bdbd60f513e5e5c8624509bfa7481f5891a842ad470cf3966b3b7f750557c4b9
Tx public key: 0f24d7cf47f2650010321819e61db3f590fa98ad22a0fe0b5f7a1a427085ed40
Timestamp: 1672614470 Timestamp [UCT]: 2023-01-01 23:07:50 Age [y:d:h:m:s]: 02:167:20:14:39
Block: 665567 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 641583 RingCT/type: yes/0
Extra: 010f24d7cf47f2650010321819e61db3f590fa98ad22a0fe0b5f7a1a427085ed400211000000035029cbac000000000000000000

1 output(s) for total of 3.825605672000 dcy

stealth address amount amount idx
00: 9bfa9ec8f051984d886e0bb7019a2f43213896f538a141d7ab4b5f364293df26 3.825605672000 1106616 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 dinasty-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": 665577, "vin": [ { "gen": { "height": 665567 } } ], "vout": [ { "amount": 3825605672, "target": { "key": "9bfa9ec8f051984d886e0bb7019a2f43213896f538a141d7ab4b5f364293df26" } } ], "extra": [ 1, 15, 36, 215, 207, 71, 242, 101, 0, 16, 50, 24, 25, 230, 29, 179, 245, 144, 250, 152, 173, 34, 160, 254, 11, 95, 122, 26, 66, 112, 133, 237, 64, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8