Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f24760df93a55282e971eaa31fdc3c656eecd23ac90e04356fdf28444af690aa

Tx prefix hash: 36623bc670a86e0ab8bd4b8819b2c14b12fdc717787eb84d7079d1f08b8adbf2
Tx public key: b94bd8e675cf0a00b269631dfe5aff8a7b99afdcf5e5432b427b8a88dcdd2dbd
Timestamp: 1713162118 Timestamp [UCT]: 2024-04-15 06:21:58 Age [y:d:h:m:s]: 00:351:04:23:22
Block: 1000855 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251063 RingCT/type: yes/0
Extra: 01b94bd8e675cf0a00b269631dfe5aff8a7b99afdcf5e5432b427b8a88dcdd2dbd02110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ada81609618ecace46356ae9fe690f208b9f5f9f7115b4748cacf21bd911d1ce 0.600000000000 1461355 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": 1000865, "vin": [ { "gen": { "height": 1000855 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ada81609618ecace46356ae9fe690f208b9f5f9f7115b4748cacf21bd911d1ce" } } ], "extra": [ 1, 185, 75, 216, 230, 117, 207, 10, 0, 178, 105, 99, 29, 254, 90, 255, 138, 123, 153, 175, 220, 245, 229, 67, 43, 66, 123, 138, 136, 220, 221, 45, 189, 2, 17, 0, 0, 0, 4, 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