Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3b567d8891709fc0be2e20f52a113a30ebf5225e0b31335b761dece5d31dfce

Tx prefix hash: 5467f97888544cd81ed5f81b7fda7c6127bf8a0a98004a630d624425c8af35b4
Tx public key: 2c4278641befb8452f259d3fea9af6d8d1b8587994ce10731f7e17af6918d906
Timestamp: 1721190654 Timestamp [UCT]: 2024-07-17 04:30:54 Age [y:d:h:m:s]: 00:240:05:17:36
Block: 1067437 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171606 RingCT/type: yes/0
Extra: 012c4278641befb8452f259d3fea9af6d8d1b8587994ce10731f7e17af6918d90602110000001291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25e029fe42f92919eea9afc326e00b6aeb78ed0355fdcc2245493bf5d18693e2 0.600000000000 1538246 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": 1067447, "vin": [ { "gen": { "height": 1067437 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25e029fe42f92919eea9afc326e00b6aeb78ed0355fdcc2245493bf5d18693e2" } } ], "extra": [ 1, 44, 66, 120, 100, 27, 239, 184, 69, 47, 37, 157, 63, 234, 154, 246, 216, 209, 184, 88, 121, 148, 206, 16, 115, 31, 126, 23, 175, 105, 24, 217, 6, 2, 17, 0, 0, 0, 18, 145, 225, 60, 4, 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