Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6e684ab04e68fe252f6dcccbe092454f01c77a7000a216ad5e0894f4dbd8df0

Tx prefix hash: 1eb761e6e1f9c90cf63afa888076949dd2812327bfd1b26e1fc4a1e144a603b0
Tx public key: d243c9561c4baa28012570398ebd3aa359b89a81f6b1772215d0ddf0e7d77d25
Timestamp: 1723627192 Timestamp [UCT]: 2024-08-14 09:19:52 Age [y:d:h:m:s]: 00:166:16:29:34
Block: 1087631 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118990 RingCT/type: yes/0
Extra: 01d243c9561c4baa28012570398ebd3aa359b89a81f6b1772215d0ddf0e7d77d2502110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 449111bb90a5a4e9354d27037e82c030a91a120f4d2ea53b5adb33bd196fb28c 0.600000000000 1562240 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": 1087641, "vin": [ { "gen": { "height": 1087631 } } ], "vout": [ { "amount": 600000000, "target": { "key": "449111bb90a5a4e9354d27037e82c030a91a120f4d2ea53b5adb33bd196fb28c" } } ], "extra": [ 1, 210, 67, 201, 86, 28, 75, 170, 40, 1, 37, 112, 57, 142, 189, 58, 163, 89, 184, 154, 129, 246, 177, 119, 34, 21, 208, 221, 240, 231, 215, 125, 37, 2, 17, 0, 0, 0, 4, 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