Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2303dd470c1ac7036b1a613ee76794a5723646fb63ef2dadbe77a9ec266425fc

Tx prefix hash: 76e632ef79420feea03ff6de0168e240a567e40b9ebf10175705d3beb5cade7c
Tx public key: 537715a9c2ce2628dd390b751ea53a4104011e3a964aeeae8a97c6c8f0528751
Timestamp: 1716751496 Timestamp [UCT]: 2024-05-26 19:24:56 Age [y:d:h:m:s]: 00:311:19:01:30
Block: 1030634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222828 RingCT/type: yes/0
Extra: 01537715a9c2ce2628dd390b751ea53a4104011e3a964aeeae8a97c6c8f052875102110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0f001b82c611191b65a1769f753d29d39bc5a66a83292e4ae3f6fd7acf27763 0.600000000000 1498891 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": 1030644, "vin": [ { "gen": { "height": 1030634 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0f001b82c611191b65a1769f753d29d39bc5a66a83292e4ae3f6fd7acf27763" } } ], "extra": [ 1, 83, 119, 21, 169, 194, 206, 38, 40, 221, 57, 11, 117, 30, 165, 58, 65, 4, 1, 30, 58, 150, 74, 238, 174, 138, 151, 198, 200, 240, 82, 135, 81, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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