Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc75f6a120d2fb5031d6101998944be280c8c3a42ccb039412527c4ea99cb576

Tx prefix hash: 2ace0396cdeff3a2289e3c1ab422710f2bbbc6d75fb48faef074fc019fcff6bb
Tx public key: 154520da37a850e566b088052c3dcc8ae3b1434714e9e7486a89d3c23460b778
Timestamp: 1632544268 Timestamp [UCT]: 2021-09-25 04:31:08 Age [y:d:h:m:s]: 03:132:09:26:03
Block: 340397 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 870842 RingCT/type: yes/0
Extra: 01154520da37a850e566b088052c3dcc8ae3b1434714e9e7486a89d3c23460b778021100000019f29d7abf000000000000000000

1 output(s) for total of 45.721857424000 dcy

stealth address amount amount idx
00: b016b62a47e1f4a9a1273755a9ea5da79a73fa1950fb1cabbd8390e88a6f45f2 45.721857424000 699644 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": 340407, "vin": [ { "gen": { "height": 340397 } } ], "vout": [ { "amount": 45721857424, "target": { "key": "b016b62a47e1f4a9a1273755a9ea5da79a73fa1950fb1cabbd8390e88a6f45f2" } } ], "extra": [ 1, 21, 69, 32, 218, 55, 168, 80, 229, 102, 176, 136, 5, 44, 61, 204, 138, 227, 177, 67, 71, 20, 233, 231, 72, 106, 137, 211, 194, 52, 96, 183, 120, 2, 17, 0, 0, 0, 25, 242, 157, 122, 191, 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