Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 636cbb8637840f72459cb74a02a169e03a19d49815456fac42f5b4ea3ce66893

Tx prefix hash: 55e5b4226a19bd8f52938491468a514b8669655d4e7bb182e3ad223706bfea8c
Tx public key: e9e75625ec56257ada3c3f7211ce21d575b4bac2e893ee054becc6806c81c3c9
Timestamp: 1721677510 Timestamp [UCT]: 2024-07-22 19:45:10 Age [y:d:h:m:s]: 00:269:19:47:21
Block: 1071451 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192786 RingCT/type: yes/0
Extra: 01e9e75625ec56257ada3c3f7211ce21d575b4bac2e893ee054becc6806c81c3c902110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 10cfbe1238b37b19c40c24936c8e5903f6e67aa8aa88728d4d4f295a57c5bca9 0.600000000000 1543688 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": 1071461, "vin": [ { "gen": { "height": 1071451 } } ], "vout": [ { "amount": 600000000, "target": { "key": "10cfbe1238b37b19c40c24936c8e5903f6e67aa8aa88728d4d4f295a57c5bca9" } } ], "extra": [ 1, 233, 231, 86, 37, 236, 86, 37, 122, 218, 60, 63, 114, 17, 206, 33, 213, 117, 180, 186, 194, 232, 147, 238, 5, 75, 236, 198, 128, 108, 129, 195, 201, 2, 17, 0, 0, 0, 3, 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