Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d9584845d02f0fcc482a4b8f83b658b253807a4346f0a1b8841c18814d93302

Tx prefix hash: 1415292367c7ecb45d2adf89e7d7ace90766ef68850530ec7ca168a307a2da88
Tx public key: 2fc4016cdb37767f5481cb63c39eb2006edf1fbef46f6f9e30231c4bbf4447e7
Timestamp: 1705137375 Timestamp [UCT]: 2024-01-13 09:16:15 Age [y:d:h:m:s]: 01:141:05:06:16
Block: 934312 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362083 RingCT/type: yes/0
Extra: 012fc4016cdb37767f5481cb63c39eb2006edf1fbef46f6f9e30231c4bbf4447e70211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a98c43d18e21a8e26dc9a73df861c84c1e6366dbdac5e58299aef29c828dcfd0 0.600000000000 1392312 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": 934322, "vin": [ { "gen": { "height": 934312 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a98c43d18e21a8e26dc9a73df861c84c1e6366dbdac5e58299aef29c828dcfd0" } } ], "extra": [ 1, 47, 196, 1, 108, 219, 55, 118, 127, 84, 129, 203, 99, 195, 158, 178, 0, 110, 223, 31, 190, 244, 111, 111, 158, 48, 35, 28, 75, 191, 68, 71, 231, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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