Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df1460c8118e3d29802273a9f1a40f9d59cc0164bb9c922d4b16177e13cc5e56

Tx prefix hash: a85ab5def4c8b9ecfb968768f7366e549ab14e64e1940c967ecf77e251f998cb
Tx public key: f51c3c8aa5e4e12a7f26ebfb1ed26f2866f51ff8511883549f642c3824592fec
Timestamp: 1730024845 Timestamp [UCT]: 2024-10-27 10:27:25 Age [y:d:h:m:s]: 00:027:16:55:55
Block: 1140631 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 19786 RingCT/type: yes/0
Extra: 01f51c3c8aa5e4e12a7f26ebfb1ed26f2866f51ff8511883549f642c3824592fec021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d8e182dcc55511e473902c31dcc43bc0b5c73793384bb1d31b72c0e90bfa2c26 0.600000000000 1624432 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": 1140641, "vin": [ { "gen": { "height": 1140631 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d8e182dcc55511e473902c31dcc43bc0b5c73793384bb1d31b72c0e90bfa2c26" } } ], "extra": [ 1, 245, 28, 60, 138, 165, 228, 225, 42, 127, 38, 235, 251, 30, 210, 111, 40, 102, 245, 31, 248, 81, 24, 131, 84, 159, 100, 44, 56, 36, 89, 47, 236, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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