Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7c33ae7441173b3cdab4fc9d4003ffc3b5e987e9f188830ed69af3aac64c987

Tx prefix hash: 6b6d4c547b419b03685b90c05eae8e1519ed80e42537a64acf8a8797475e3149
Tx public key: 7d97d63f39cf785b914cec9bca4a374e1d3d99ed8214620f6d3280ed23b8255c
Timestamp: 1693531575 Timestamp [UCT]: 2023-09-01 01:26:15 Age [y:d:h:m:s]: 01:290:07:56:51
Block: 838291 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 468564 RingCT/type: yes/0
Extra: 017d97d63f39cf785b914cec9bca4a374e1d3d99ed8214620f6d3280ed23b8255c021100000002e6d27f9c000000000000000000

1 output(s) for total of 1.024221763000 dcy

stealth address amount amount idx
00: 679d9e5bbd741618194490fb14668bb0451da2ad6620b2605243cffabd7530d5 1.024221763000 1291011 of 0

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": 838301, "vin": [ { "gen": { "height": 838291 } } ], "vout": [ { "amount": 1024221763, "target": { "key": "679d9e5bbd741618194490fb14668bb0451da2ad6620b2605243cffabd7530d5" } } ], "extra": [ 1, 125, 151, 214, 63, 57, 207, 120, 91, 145, 76, 236, 155, 202, 74, 55, 78, 29, 61, 153, 237, 130, 20, 98, 15, 109, 50, 128, 237, 35, 184, 37, 92, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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