Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28ff874079a42cbf5ed16426bf31f30c66591b01e65ce8661f95c69decccd704

Tx prefix hash: 54da93d4f27f60fb990c036bb39ec40ace441559a26e2a56da938c216223f064
Tx public key: c1dc303db8b3ef004e7a8d9a92c932804661153e996d1460572eb49a81c87c3b
Timestamp: 1578920807 Timestamp [UCT]: 2020-01-13 13:06:47 Age [y:d:h:m:s]: 05:040:02:30:13
Block: 44629 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1178819 RingCT/type: yes/0
Extra: 01c1dc303db8b3ef004e7a8d9a92c932804661153e996d1460572eb49a81c87c3b0211000000104943cd9f000000000000000000

1 output(s) for total of 436.642934922000 dcy

stealth address amount amount idx
00: c3cb8e09b9c1cecd08ecde43a911963e16b8de6ff88287605e86be8ed8d84515 436.642934922000 81272 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": 44639, "vin": [ { "gen": { "height": 44629 } } ], "vout": [ { "amount": 436642934922, "target": { "key": "c3cb8e09b9c1cecd08ecde43a911963e16b8de6ff88287605e86be8ed8d84515" } } ], "extra": [ 1, 193, 220, 48, 61, 184, 179, 239, 0, 78, 122, 141, 154, 146, 201, 50, 128, 70, 97, 21, 62, 153, 109, 20, 96, 87, 46, 180, 154, 129, 200, 124, 59, 2, 17, 0, 0, 0, 16, 73, 67, 205, 159, 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