Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb21514de9050f2e0a6ffa6f1153647747d10945c69311f11d096c77b0190734

Tx prefix hash: 050296c6b78296f2d1c8164723454d5730b3fb24e0f9ba112d9ca203e0c154cd
Tx public key: 671dfa521f2ac335dd95a180210dc2a415b9f72942b8bd376e8e582def6a7669
Timestamp: 1708290756 Timestamp [UCT]: 2024-02-18 21:12:36 Age [y:d:h:m:s]: 00:270:06:05:30
Block: 960480 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 193484 RingCT/type: yes/0
Extra: 01671dfa521f2ac335dd95a180210dc2a415b9f72942b8bd376e8e582def6a766902110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 752621f6a0566ed901e9498a12c66b56b209775744b02414439033e8eee83915 0.600000000000 1420049 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": 960490, "vin": [ { "gen": { "height": 960480 } } ], "vout": [ { "amount": 600000000, "target": { "key": "752621f6a0566ed901e9498a12c66b56b209775744b02414439033e8eee83915" } } ], "extra": [ 1, 103, 29, 250, 82, 31, 42, 195, 53, 221, 149, 161, 128, 33, 13, 194, 164, 21, 185, 247, 41, 66, 184, 189, 55, 110, 142, 88, 45, 239, 106, 118, 105, 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