Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6456859cbdb820d95acbfc0f75f49cdca794d91b5ec59da0ff2a2d44b0b338ff

Tx prefix hash: 944e0cff458f77a7bd1064af8eff9dc87d168bc9fa41fd6c79251ae4ca44b800
Tx public key: 2eabb6966d9b8a7f1b515323fd6d6ff60e42ca8db549878d1c17553b712889df
Timestamp: 1732043975 Timestamp [UCT]: 2024-11-19 19:19:35 Age [y:d:h:m:s]: 01:043:05:06:53
Block: 1157318 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289357 RingCT/type: yes/0
Extra: 012eabb6966d9b8a7f1b515323fd6d6ff60e42ca8db549878d1c17553b712889df021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 03636774f2ce0373bdc2b95e4e82b2ef98bb2cd60723d07b5b8ec74aaf93544c 0.600000000000 1642941 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": 1157328, "vin": [ { "gen": { "height": 1157318 } } ], "vout": [ { "amount": 600000000, "target": { "key": "03636774f2ce0373bdc2b95e4e82b2ef98bb2cd60723d07b5b8ec74aaf93544c" } } ], "extra": [ 1, 46, 171, 182, 150, 109, 155, 138, 127, 27, 81, 83, 35, 253, 109, 111, 246, 14, 66, 202, 141, 181, 73, 135, 141, 28, 23, 85, 59, 113, 40, 137, 223, 2, 17, 0, 0, 0, 2, 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