Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f97f5415516d6083d2d3857b65fea355cd36c5a88a6e6435bd1eab93ac9df5f4

Tx prefix hash: 4996e505cf0a29b92ff40996574ca9c1945ff234e4e80e3ec0c0b9fc8a64059d
Tx public key: a5c4c878279dbd498ac15ea0b53b2142ecc96df8281291ebe9dec23a5a05806a
Timestamp: 1679885580 Timestamp [UCT]: 2023-03-27 02:53:00 Age [y:d:h:m:s]: 02:024:08:23:13
Block: 725884 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 538930 RingCT/type: yes/0
Extra: 01a5c4c878279dbd498ac15ea0b53b2142ecc96df8281291ebe9dec23a5a05806a02110000000175e3f0e9000000000000000000

1 output(s) for total of 2.415250119000 dcy

stealth address amount amount idx
00: d8dc0e1c6658fb8f6e43a3a86e6a7d86df9f82c65010a0f8dc6aa4d6a2acbd1d 2.415250119000 1171095 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": 725894, "vin": [ { "gen": { "height": 725884 } } ], "vout": [ { "amount": 2415250119, "target": { "key": "d8dc0e1c6658fb8f6e43a3a86e6a7d86df9f82c65010a0f8dc6aa4d6a2acbd1d" } } ], "extra": [ 1, 165, 196, 200, 120, 39, 157, 189, 73, 138, 193, 94, 160, 181, 59, 33, 66, 236, 201, 109, 248, 40, 18, 145, 235, 233, 222, 194, 58, 90, 5, 128, 106, 2, 17, 0, 0, 0, 1, 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