Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4605e806e8e1cb4fa016bab375c12147c1a1f39b9e50822d1de2211ff7b3ae35

Tx prefix hash: a4e8744c62e8632131070e0dadad12e9328003537fbeddf05759dbc7106ea174
Tx public key: ac43f2e8e4691cd50a23e88122e9d755a5f8f55e354fd924cd007648a343c0b4
Timestamp: 1708221327 Timestamp [UCT]: 2024-02-18 01:55:27 Age [y:d:h:m:s]: 01:087:02:11:24
Block: 959897 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323304 RingCT/type: yes/0
Extra: 01ac43f2e8e4691cd50a23e88122e9d755a5f8f55e354fd924cd007648a343c0b40211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7a4a9739d63aa305c19d8eaec3ada17fd72f23e9423a850b5a1180dfe467960 0.600000000000 1419456 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": 959907, "vin": [ { "gen": { "height": 959897 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7a4a9739d63aa305c19d8eaec3ada17fd72f23e9423a850b5a1180dfe467960" } } ], "extra": [ 1, 172, 67, 242, 232, 228, 105, 28, 213, 10, 35, 232, 129, 34, 233, 215, 85, 165, 248, 245, 94, 53, 79, 217, 36, 205, 0, 118, 72, 163, 67, 192, 180, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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