Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5c6862e635cabea2ae6e1032994796f16b31fbf3fd0ab5352ac81e3254dd8d4

Tx prefix hash: d126fb230e453556d0e718bc8c1d6ba79c01366fd66437e764d6e71e96b0413b
Tx public key: 19e201171ea9a9f976ce08df896f2692d16ae51ef2d3417eb21b73831214847b
Timestamp: 1645787934 Timestamp [UCT]: 2022-02-25 11:18:54 Age [y:d:h:m:s]: 03:016:11:08:16
Block: 446167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 791817 RingCT/type: yes/0
Extra: 0119e201171ea9a9f976ce08df896f2692d16ae51ef2d3417eb21b73831214847b0211000000142e6b1fd5000000000000000000

1 output(s) for total of 20.401579906000 dcy

stealth address amount amount idx
00: e23057eea156ed6a15bfdd65a6efc6efe199bf59c673f16aa1b30a2b86779ec7 20.401579906000 859972 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": 446177, "vin": [ { "gen": { "height": 446167 } } ], "vout": [ { "amount": 20401579906, "target": { "key": "e23057eea156ed6a15bfdd65a6efc6efe199bf59c673f16aa1b30a2b86779ec7" } } ], "extra": [ 1, 25, 226, 1, 23, 30, 169, 169, 249, 118, 206, 8, 223, 137, 111, 38, 146, 209, 106, 229, 30, 242, 211, 65, 126, 178, 27, 115, 131, 18, 20, 132, 123, 2, 17, 0, 0, 0, 20, 46, 107, 31, 213, 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