Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 893908232d27b6bfe467071e262f867142e8c995fd9ff74fd8bacdd38c9d1a5d

Tx prefix hash: 595a0679ca7d2d5ad96da350145daba89d8f99ca3b1b68b6e3e5014f54ed71be
Tx public key: 065b69a0d515edd592092961fa8d6ae5af7f22e8de88da84603efb4c331b4c65
Timestamp: 1681684426 Timestamp [UCT]: 2023-04-16 22:33:46 Age [y:d:h:m:s]: 02:039:01:58:27
Block: 740136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 550123 RingCT/type: yes/0
Extra: 01065b69a0d515edd592092961fa8d6ae5af7f22e8de88da84603efb4c331b4c65021100000001b3164c24000000000000000000

1 output(s) for total of 2.165820223000 dcy

stealth address amount amount idx
00: 0e474777681f2baec1390f41c6ba27423bbf8c5af0ede18e17e0b5ca0541b996 2.165820223000 1187017 of 0

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": 740146, "vin": [ { "gen": { "height": 740136 } } ], "vout": [ { "amount": 2165820223, "target": { "key": "0e474777681f2baec1390f41c6ba27423bbf8c5af0ede18e17e0b5ca0541b996" } } ], "extra": [ 1, 6, 91, 105, 160, 213, 21, 237, 213, 146, 9, 41, 97, 250, 141, 106, 229, 175, 127, 34, 232, 222, 136, 218, 132, 96, 62, 251, 76, 51, 27, 76, 101, 2, 17, 0, 0, 0, 1, 179, 22, 76, 36, 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