Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 250d6e099fa282d2577edc6a88a3eab646ab74f5a508f7cb2e34fca951a3ebd5

Tx prefix hash: 707824e9e9832c9f1bf73f60143783acfbe12e70b5040467ed406af76045cb68
Tx public key: d38045d35225cc3c036c7a41b695963b5e40cb4172d52ea1bdc5d33f4102a572
Timestamp: 1673526479 Timestamp [UCT]: 2023-01-12 12:27:59 Age [y:d:h:m:s]: 02:300:18:21:17
Block: 673127 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 734351 RingCT/type: yes/0
Extra: 01d38045d35225cc3c036c7a41b695963b5e40cb4172d52ea1bdc5d33f4102a5720211000000078b7b6602000000000000000000

1 output(s) for total of 3.611193611000 dcy

stealth address amount amount idx
00: f7f9f169c424ab4a2d8a228d9d3ab5be950fb1143ad1086d106c4067e7576ea6 3.611193611000 1114716 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": 673137, "vin": [ { "gen": { "height": 673127 } } ], "vout": [ { "amount": 3611193611, "target": { "key": "f7f9f169c424ab4a2d8a228d9d3ab5be950fb1143ad1086d106c4067e7576ea6" } } ], "extra": [ 1, 211, 128, 69, 211, 82, 37, 204, 60, 3, 108, 122, 65, 182, 149, 150, 59, 94, 64, 203, 65, 114, 213, 46, 161, 189, 197, 211, 63, 65, 2, 165, 114, 2, 17, 0, 0, 0, 7, 139, 123, 102, 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