Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f727c4eb91e62db1bcc741539e60134bc69f42861cc6512a695e31b593a63157

Tx prefix hash: f506824514667d4cc2da9c42604e84ae6c6266684a5e081e40af1b02688b30f8
Tx public key: dd959d39b003b69a5801d88a4337a5db12428ce05327c403fa746c67ff87f2ef
Timestamp: 1705225474 Timestamp [UCT]: 2024-01-14 09:44:34 Age [y:d:h:m:s]: 01:065:01:47:08
Block: 935058 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307614 RingCT/type: yes/0
Extra: 01dd959d39b003b69a5801d88a4337a5db12428ce05327c403fa746c67ff87f2ef021100000003bfa22221000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3cd7d8365d7bd5e83e6f06d0a643a43d7af476b957b6ac0b5684c9154e46f81c 0.600000000000 1393074 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": 935068, "vin": [ { "gen": { "height": 935058 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3cd7d8365d7bd5e83e6f06d0a643a43d7af476b957b6ac0b5684c9154e46f81c" } } ], "extra": [ 1, 221, 149, 157, 57, 176, 3, 182, 154, 88, 1, 216, 138, 67, 55, 165, 219, 18, 66, 140, 224, 83, 39, 196, 3, 250, 116, 108, 103, 255, 135, 242, 239, 2, 17, 0, 0, 0, 3, 191, 162, 34, 33, 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