Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f4e9f3799387a830344f443e4ea27c361a152452e2b0762287b52fc5bdcdf468

Tx prefix hash: de37200bc7da3f9281fcc7704b2dbd75c2b2eabac2f35c8d06ad7aae479d5d7c
Tx public key: 21a5cf41043df70b49a90f52618264ac33b39bfcb5e170278d837e15ff1baa4b
Timestamp: 1719111402 Timestamp [UCT]: 2024-06-23 02:56:42 Age [y:d:h:m:s]: 00:267:08:13:56
Block: 1050170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191064 RingCT/type: yes/0
Extra: 0121a5cf41043df70b49a90f52618264ac33b39bfcb5e170278d837e15ff1baa4b02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d9a0139d6aff8c815d158aa7050382547f6e4ff1e9ee2efe8bf2fbd42cfc51c 0.600000000000 1520331 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": 1050180, "vin": [ { "gen": { "height": 1050170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d9a0139d6aff8c815d158aa7050382547f6e4ff1e9ee2efe8bf2fbd42cfc51c" } } ], "extra": [ 1, 33, 165, 207, 65, 4, 61, 247, 11, 73, 169, 15, 82, 97, 130, 100, 172, 51, 179, 155, 252, 181, 225, 112, 39, 141, 131, 126, 21, 255, 27, 170, 75, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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