Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1e0ec6f1ad77a744b82e447a301480ffd55e2bfc47738e89f95ef2e410884e4

Tx prefix hash: 2bc8b5db5aabda3db0966335f71c1635402104c04f2e860c023820ad178a3c1e
Tx public key: fea2d2cb75a985a92ef4f46298f7985dc5131bbf3142a3c912609260c4b26bd6
Timestamp: 1734046770 Timestamp [UCT]: 2024-12-12 23:39:30 Age [y:d:h:m:s]: 00:109:20:45:27
Block: 1173921 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 78280 RingCT/type: yes/0
Extra: 01fea2d2cb75a985a92ef4f46298f7985dc5131bbf3142a3c912609260c4b26bd6021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a170dee44a4f8ccee424280c55f3b6efd10e4a42b645f72d1a898435aa783d4f 0.600000000000 1660010 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": 1173931, "vin": [ { "gen": { "height": 1173921 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a170dee44a4f8ccee424280c55f3b6efd10e4a42b645f72d1a898435aa783d4f" } } ], "extra": [ 1, 254, 162, 210, 203, 117, 169, 133, 169, 46, 244, 244, 98, 152, 247, 152, 93, 197, 19, 27, 191, 49, 66, 163, 201, 18, 96, 146, 96, 196, 178, 107, 214, 2, 17, 0, 0, 0, 1, 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