Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1d784d2c62be5f7b8ab58cd15b9397add0092d28c1920c1e273ee7782e2c90f

Tx prefix hash: af02f3236cee56933f5517ee24c734f3ee1a6897c159aa354a3e0686d2dcde49
Tx public key: b591a99ef97cc6e1b35509bd23f255883d5d39238e4a33ea22bc530ef9fa1258
Timestamp: 1705571290 Timestamp [UCT]: 2024-01-18 09:48:10 Age [y:d:h:m:s]: 01:309:10:58:24
Block: 937919 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 479986 RingCT/type: yes/0
Extra: 01b591a99ef97cc6e1b35509bd23f255883d5d39238e4a33ea22bc530ef9fa125802110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd251ff2a69ac0e6a88368862e66d6cf191f7e584943c61fa513863966eed519 0.600000000000 1395983 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 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": 937929, "vin": [ { "gen": { "height": 937919 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd251ff2a69ac0e6a88368862e66d6cf191f7e584943c61fa513863966eed519" } } ], "extra": [ 1, 181, 145, 169, 158, 249, 124, 198, 225, 179, 85, 9, 189, 35, 242, 85, 136, 61, 93, 57, 35, 142, 74, 51, 234, 34, 188, 83, 14, 249, 250, 18, 88, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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