Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 365977561148f23519cda4ddd27a6e473a68f5d85d55eca449c6dc37e8140133

Tx prefix hash: 55b403dd4013737cc25d2797cd39e0c9ba6a2126227c566206956590880d2335
Tx public key: 90a42ae4f4c8026b8f1848aa61aac01ce571c203a5cb27103f632ce80bf2a6e1
Timestamp: 1699864221 Timestamp [UCT]: 2023-11-13 08:30:21 Age [y:d:h:m:s]: 01:142:22:42:52
Block: 890621 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 363348 RingCT/type: yes/0
Extra: 0190a42ae4f4c8026b8f1848aa61aac01ce571c203a5cb27103f632ce80bf2a6e102110000000675e3f0e9000000000000000000

1 output(s) for total of 0.687073043000 dcy

stealth address amount amount idx
00: c1943a7545cd92bb7bbd789c96403db9a1d5cca64740e3e6f19f9b953cb3d11c 0.687073043000 1346646 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": 890631, "vin": [ { "gen": { "height": 890621 } } ], "vout": [ { "amount": 687073043, "target": { "key": "c1943a7545cd92bb7bbd789c96403db9a1d5cca64740e3e6f19f9b953cb3d11c" } } ], "extra": [ 1, 144, 164, 42, 228, 244, 200, 2, 107, 143, 24, 72, 170, 97, 170, 192, 28, 229, 113, 194, 3, 165, 203, 39, 16, 63, 99, 44, 232, 11, 242, 166, 225, 2, 17, 0, 0, 0, 6, 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