Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 683d1dddfa48f228ab1c67007c500f12116a378627b6fd2df0f0e1856b43492f

Tx prefix hash: b501081bd031d4e292ebc94adb9c5005f49570e0179945b9b2ef9143729c05ff
Tx public key: a6d6a57992069317e83bca95a1b7e201ee08b607434203b80a9c29a5ad342d8d
Timestamp: 1704999199 Timestamp [UCT]: 2024-01-11 18:53:19 Age [y:d:h:m:s]: 01:138:20:22:03
Block: 933176 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360382 RingCT/type: yes/0
Extra: 01a6d6a57992069317e83bca95a1b7e201ee08b607434203b80a9c29a5ad342d8d0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: efe0ec5f124aece239397550ab2d2b5f86d7566a143aecf46ceb6fd0a5a4aaf9 0.600000000000 1391134 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": 933186, "vin": [ { "gen": { "height": 933176 } } ], "vout": [ { "amount": 600000000, "target": { "key": "efe0ec5f124aece239397550ab2d2b5f86d7566a143aecf46ceb6fd0a5a4aaf9" } } ], "extra": [ 1, 166, 214, 165, 121, 146, 6, 147, 23, 232, 59, 202, 149, 161, 183, 226, 1, 238, 8, 182, 7, 67, 66, 3, 184, 10, 156, 41, 165, 173, 52, 45, 141, 2, 17, 0, 0, 0, 7, 122, 156, 244, 199, 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