Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 816e86ce31713b7dbd5b35189f3648d568144d9b24690d969a0495c104978f36

Tx prefix hash: 0f489b4957fa9a6dbb8bcc6541fbe2bcb9b53d45305ddfda91bec284feb1a504
Tx public key: 41df7f801834e768b60538adddbffd0f052a5b6f658b9d0126724729753709a9
Timestamp: 1657159500 Timestamp [UCT]: 2022-07-07 02:05:00 Age [y:d:h:m:s]: 02:183:23:17:15
Block: 538279 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 652844 RingCT/type: yes/0
Extra: 0141df7f801834e768b60538adddbffd0f052a5b6f658b9d0126724729753709a9021100000001cb8520c2000000000000000000

1 output(s) for total of 10.103186553000 dcy

stealth address amount amount idx
00: 6575a4f310fc409d3a00e72f9aa56a20b4dd4fd09c048ceb88a172ca6e12f5d3 10.103186553000 968260 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": 538289, "vin": [ { "gen": { "height": 538279 } } ], "vout": [ { "amount": 10103186553, "target": { "key": "6575a4f310fc409d3a00e72f9aa56a20b4dd4fd09c048ceb88a172ca6e12f5d3" } } ], "extra": [ 1, 65, 223, 127, 128, 24, 52, 231, 104, 182, 5, 56, 173, 221, 191, 253, 15, 5, 42, 91, 111, 101, 139, 157, 1, 38, 114, 71, 41, 117, 55, 9, 169, 2, 17, 0, 0, 0, 1, 203, 133, 32, 194, 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