Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57556492f77019c93639da1d5e04d0c445120152ed9ec8d7e671901a4239b346

Tx prefix hash: ccafc73b8b6ca931ec119a0a5b2e5d597b1b11d707fc904aee6b97996b8a7d2e
Tx public key: 7afb5af586172c6f49df07fb65f4075a854893f067959a8d0e007923d4fbcdfe
Timestamp: 1694958484 Timestamp [UCT]: 2023-09-17 13:48:04 Age [y:d:h:m:s]: 01:128:02:10:19
Block: 850137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 352813 RingCT/type: yes/0
Extra: 017afb5af586172c6f49df07fb65f4075a854893f067959a8d0e007923d4fbcdfe02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.935714300000 dcy

stealth address amount amount idx
00: ac837aa00062e7ad07e787f799148307de955bffd56fc1667979f7baca9f56fd 0.935714300000 1303835 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": 850147, "vin": [ { "gen": { "height": 850137 } } ], "vout": [ { "amount": 935714300, "target": { "key": "ac837aa00062e7ad07e787f799148307de955bffd56fc1667979f7baca9f56fd" } } ], "extra": [ 1, 122, 251, 90, 245, 134, 23, 44, 111, 73, 223, 7, 251, 101, 244, 7, 90, 133, 72, 147, 240, 103, 149, 154, 141, 14, 0, 121, 35, 212, 251, 205, 254, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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