Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f95b3b9f97c812e740dbcac0fc496d75e5a13c5f16074afd1a53f46370063040

Tx prefix hash: 216cd8105fc71b5673ad94e9d7145f3f92d189aabe0692f027eb129178a42e9b
Tx public key: 1712f276f0207bb2719979a9ad7a68690bc4b8d30092cd88b7c4378af4bfa50c
Timestamp: 1583540941 Timestamp [UCT]: 2020-03-07 00:29:01 Age [y:d:h:m:s]: 04:339:21:45:10
Block: 78040 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1137041 RingCT/type: yes/0
Extra: 011712f276f0207bb2719979a9ad7a68690bc4b8d30092cd88b7c4378af4bfa50c0211000000334ac5aa02000000000000000000

1 output(s) for total of 338.393394446000 dcy

stealth address amount amount idx
00: a95167cd39e4f4321c217f72458a8dcdd77c9beb6e2a2ca9fe20d721db10ee75 338.393394446000 143297 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": 78050, "vin": [ { "gen": { "height": 78040 } } ], "vout": [ { "amount": 338393394446, "target": { "key": "a95167cd39e4f4321c217f72458a8dcdd77c9beb6e2a2ca9fe20d721db10ee75" } } ], "extra": [ 1, 23, 18, 242, 118, 240, 32, 123, 178, 113, 153, 121, 169, 173, 122, 104, 105, 11, 196, 184, 211, 0, 146, 205, 136, 183, 196, 55, 138, 244, 191, 165, 12, 2, 17, 0, 0, 0, 51, 74, 197, 170, 2, 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