Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f25d0bdedce1a9a2a8e3be84ea1e0ac4e65f888275df9e864fb66fe484ba7236

Tx prefix hash: 67493bf2e2d66ff51f4c021a61a1814fc218395f174a9798d255d15e2b0002fb
Tx public key: c6382c19ae18c2812879fa5dd9634c287666ae1a7a82250bc9ce946324393317
Timestamp: 1700802483 Timestamp [UCT]: 2023-11-24 05:08:03 Age [y:d:h:m:s]: 01:349:18:18:54
Block: 898391 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 508867 RingCT/type: yes/0
Extra: 01c6382c19ae18c2812879fa5dd9634c287666ae1a7a82250bc9ce94632439331702110000000175e3f0e9000000000000000000

1 output(s) for total of 0.647526673000 dcy

stealth address amount amount idx
00: 0174783fc2831ba9b08d4fd7bff57a3bc1579dccc0489b3f156cd2764feb57f5 0.647526673000 1354804 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": 898401, "vin": [ { "gen": { "height": 898391 } } ], "vout": [ { "amount": 647526673, "target": { "key": "0174783fc2831ba9b08d4fd7bff57a3bc1579dccc0489b3f156cd2764feb57f5" } } ], "extra": [ 1, 198, 56, 44, 25, 174, 24, 194, 129, 40, 121, 250, 93, 217, 99, 76, 40, 118, 102, 174, 26, 122, 130, 37, 11, 201, 206, 148, 99, 36, 57, 51, 23, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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