Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 737b4b9dc9fe115f9d295a56436de63c2cb88b9cac1a3696e40e579b8daea32f

Tx prefix hash: 220807265fdb519287d3b6d8c14fd98bf312f725cd01eec324f58b97478b3b7d
Tx public key: ccaeca725d015e6cfbe85c86b3f1a1779a2483c5271a155de51eb210e0a86daa
Timestamp: 1737412544 Timestamp [UCT]: 2025-01-20 22:35:44 Age [y:d:h:m:s]: 00:151:22:36:49
Block: 1201714 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108295 RingCT/type: yes/0
Extra: 01ccaeca725d015e6cfbe85c86b3f1a1779a2483c5271a155de51eb210e0a86daa021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c471c377c667adf04c31aa7e3604d92916a7a4cd3177ee10ca7e03bc40234d4 0.600000000000 1688371 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": 1201724, "vin": [ { "gen": { "height": 1201714 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c471c377c667adf04c31aa7e3604d92916a7a4cd3177ee10ca7e03bc40234d4" } } ], "extra": [ 1, 204, 174, 202, 114, 93, 1, 94, 108, 251, 232, 92, 134, 179, 241, 161, 119, 154, 36, 131, 197, 39, 26, 21, 93, 229, 30, 178, 16, 224, 168, 109, 170, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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